@withpica/mcp-server-directory 1.2.0 → 1.3.0

package/dist/prompts/index.js

@@ -1,165 +0,0 @@
-// Copyright (c) 2024-2026 Withpica Ltd. All rights reserved.
-export class PromptRegistry {
-    listPrompts() {
-        return [
-            {
-                name: "find-music",
-                description: "Find music for a sync brief, playlist, or project — search by mood, BPM, key, energy, or description",
-                arguments: [
-                    {
-                        name: "brief",
-                        description: "What you're looking for — a mood, scene description, or audio characteristics",
-                        required: false,
-                    },
-                ],
-            },
-            {
-                name: "research-creator",
-                description: "Research a songwriter, composer, or performer — see their works, identifiers, collaborators, and verification status",
-                arguments: [
-                    {
-                        name: "name_or_id",
-                        description: "Creator name, IPI number, ISNI, or MusicBrainz ID",
-                        required: false,
-                    },
-                ],
-            },
-            {
-                name: "directory-autopilot",
-                description: "Not sure where to start? Describe what you need and get routed to the right workflow — sync search, rights research, or identifier lookup",
-                arguments: [],
-            },
-        ];
-    }
-    async getPrompt(name, args) {
-        switch (name) {
-            case "find-music":
-                return this.getFindMusicPrompt(args?.brief);
-            case "research-creator":
-                return this.getResearchCreatorPrompt(args?.name_or_id);
-            case "directory-autopilot":
-                return this.getDirectoryAutopilotPrompt();
-            default:
-                throw new Error(`Prompt not found: ${name}`);
-        }
-    }
-    getFindMusicPrompt(brief) {
-        const briefInstruction = brief
-            ? `The user is looking for: "${brief}". Translate this into audio search parameters.`
-            : `Ask me what I'm looking for — a mood, a scene, a vibe, or specific audio characteristics (BPM, key, energy).`;
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: `Help me find music in the PICA public directory for a sync brief or project.
-
-${briefInstruction}
-
-Workflow:
-1. Translate the brief into search parameters for directory_search_recordings:
-   - Mood descriptions → energy, danceability, key_mode, mood filters
-   - "Upbeat" → min_energy: 0.6, min_danceability: 0.5
-   - "Dark/moody" → max_energy: 0.4, key_mode: minor
-   - "Chill" → max_energy: 0.4, max_bpm: 100
-   - Specific requests → use BPM, key, duration filters directly
-
-2. Run directory_search_recordings with the parameters.
-
-3. For each promising result, use directory_lookup_work to get:
-   - Who wrote it (credits with IPI numbers)
-   - Whether credits are attested (verified ownership)
-   - DSP links (Spotify, Apple Music — so the user can listen)
-   - Registration score (higher = cleaner rights chain)
-
-4. Present results as a shortlist with:
-   - Title, artist, BPM, key, energy
-   - Credits summary (who to contact for licensing)
-   - Any flags (unattested credits, low registration score, missing ISRC)
-
-If no results match, suggest broadening the search (wider BPM range, drop key filter, etc.).
-
-Important: This is a public directory — only works from organisations that opted in are visible. If the catalog is small, say so.`,
-                    },
-                },
-            ],
-        };
-    }
-    getResearchCreatorPrompt(nameOrId) {
-        const searchInstruction = nameOrId
-            ? `Look up: "${nameOrId}". Try directory_lookup_person first (it accepts name, IPI, ISNI, or MusicBrainz ID). If that doesn't match, use directory_list_people with a text search.`
-            : `Ask me for the creator's name, IPI number, ISNI, or MusicBrainz ID.`;
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: `Help me research a music creator in the PICA public directory.
-
-${searchInstruction}
-
-Once you find the person, use directory_lookup_person to get their complete profile:
-- Identifiers (IPI, ISNI, MusicBrainz) — essential for rights verification
-- All credited works with roles (writer, composer, performer, producer)
-- Collaborator network — who they work with
-- Verification score — how complete their profile is
-
-Then for their most notable works (up to 5), use directory_lookup_work to get:
-- Full credits and splits (are they the sole writer or one of many?)
-- Recordings with ISRCs
-- Audio analysis (BPM, key, energy)
-- DSP links and registration status
-
-Present a summary:
-- Creator profile (name, identifiers, role patterns)
-- Catalog overview (how many works, typical roles, common collaborators)
-- Notable works with credit details
-- Any gaps (missing identifiers, unattested credits, low scores)
-
-This is useful for: rights research, due diligence before licensing, publisher evaluation, or understanding a catalog before acquisition.`,
-                    },
-                },
-            ],
-        };
-    }
-    getDirectoryAutopilotPrompt() {
-        return {
-            messages: [
-                {
-                    role: "user",
-                    content: {
-                        type: "text",
-                        text: `You've connected to the PICA public music directory. Help me find what I need.
-
-First, read the llms://primer resource to understand what's available.
-
-Then ask me what I'm looking for. Based on my answer, route to the right workflow:
-
-If I'm looking for MUSIC FOR A PROJECT (sync brief, playlist, mood search):
-→ Use the find-music workflow. Translate my description into audio search parameters and search recordings by BPM, key, energy, mood. Then look up full details on promising matches.
-
-If I'm looking for INFORMATION ABOUT A CREATOR (songwriter, composer, performer):
-→ Use the research-creator workflow. Look up their profile, works, identifiers, and collaborators.
-
-If I have a SPECIFIC IDENTIFIER to resolve (ISRC, ISWC, IPI, ISNI):
-→ Route directly to the right lookup tool:
-  - ISRC (e.g. USABC1234567) → directory_lookup_isrc → then directory_lookup_work
-  - ISWC (e.g. T-123.456.789-0) → directory_lookup_work
-  - IPI or ISNI → directory_lookup_person
-  - MusicBrainz ID → directory_lookup_person
-
-If I want to BROWSE what's in the directory:
-→ Use directory_search with a broad query, or directory_list_works / directory_list_people to paginate.
-
-Tell me which workflow you chose and why, in one sentence. Offer alternatives.
-
-Important: This is a read-only public directory. I can search and look up, but I can't create or modify anything. Only works from organisations that opted into the directory are visible.`,
-                    },
-                },
-            ],
-        };
-    }
-}
-//# sourceMappingURL=index.js.map

package/dist/prompts/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AAAA,6DAA6D;AA8B7D,MAAM,OAAO,cAAc;IACzB,WAAW;QACT,OAAO;YACL;gBACE,IAAI,EAAE,YAAY;gBAClB,WAAW,EACT,sGAAsG;gBACxG,SAAS,EAAE;oBACT;wBACE,IAAI,EAAE,OAAO;wBACb,WAAW,EACT,+EAA+E;wBACjF,QAAQ,EAAE,KAAK;qBAChB;iBACF;aACF;YACD;gBACE,IAAI,EAAE,kBAAkB;gBACxB,WAAW,EACT,sHAAsH;gBACxH,SAAS,EAAE;oBACT;wBACE,IAAI,EAAE,YAAY;wBAClB,WAAW,EAAE,mDAAmD;wBAChE,QAAQ,EAAE,KAAK;qBAChB;iBACF;aACF;YACD;gBACE,IAAI,EAAE,qBAAqB;gBAC3B,WAAW,EACT,2IAA2I;gBAC7I,SAAS,EAAE,EAAE;aACd;SACF,CAAC;IACJ,CAAC;IAED,KAAK,CAAC,SAAS,CACb,IAAY,EACZ,IAA0B;QAE1B,QAAQ,IAAI,EAAE,CAAC;YACb,KAAK,YAAY;gBACf,OAAO,IAAI,CAAC,kBAAkB,CAAC,IAAI,EAAE,KAAK,CAAC,CAAC;YAC9C,KAAK,kBAAkB;gBACrB,OAAO,IAAI,CAAC,wBAAwB,CAAC,IAAI,EAAE,UAAU,CAAC,CAAC;YACzD,KAAK,qBAAqB;gBACxB,OAAO,IAAI,CAAC,2BAA2B,EAAE,CAAC;YAC5C;gBACE,MAAM,IAAI,KAAK,CAAC,qBAAqB,IAAI,EAAE,CAAC,CAAC;QACjD,CAAC;IACH,CAAC;IAEO,kBAAkB,CAAC,KAAc;QACvC,MAAM,gBAAgB,GAAG,KAAK;YAC5B,CAAC,CAAC,6BAA6B,KAAK,iDAAiD;YACrF,CAAC,CAAC,8GAA8G,CAAC;QAEnH,OAAO;YACL,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAM;oBACZ,OAAO,EAAE;wBACP,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;EAEhB,gBAAgB;;;;;;;;;;;;;;;;;;;;;;;;;kIAyBgH;qBACvH;iBACF;aACF;SACF,CAAC;IACJ,CAAC;IAEO,wBAAwB,CAAC,QAAiB;QAChD,MAAM,iBAAiB,GAAG,QAAQ;YAChC,CAAC,CAAC,aAAa,QAAQ,4JAA4J;YACnL,CAAC,CAAC,qEAAqE,CAAC;QAE1E,OAAO;YACL,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAM;oBACZ,OAAO,EAAE;wBACP,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;EAEhB,iBAAiB;;;;;;;;;;;;;;;;;;;;0IAoBuH;qBAC/H;iBACF;aACF;SACF,CAAC;IACJ,CAAC;IAEO,2BAA2B;QACjC,OAAO;YACL,QAAQ,EAAE;gBACR;oBACE,IAAI,EAAE,MAAM;oBACZ,OAAO,EAAE;wBACP,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;2LAwByK;qBAChL;iBACF;aACF;SACF,CAAC;IACJ,CAAC;CACF"}

package/dist/prompts/public-question-atlas.d.ts

@@ -1,121 +0,0 @@
-/**
- * Public Question Atlas — ADR-229 Decision 1.
- *
- * Source-of-truth registry mapping natural public-discovery questions to
- * the canonical directory-MCP tool resolution. Sister of:
- *   - `mcp-server/src/prompts/creator-question-atlas.ts` (ADR-226, customer)
- *   - `team-mcp-server/src/prompts/operator-question-atlas.ts` (ADR-228, operator)
- *
- * Read by:
- *
- *   - lint Rule 11F (extended in ADR-229) — validates every `directory_*`
- *     tool's `Use when the user asks` block cites questions resolving
- *     here, rejects creator/operator atlas cross-pollination, asserts
- *     mutual exclusivity of `clean_empty_state` and `fallback_when_empty`,
- *     and asserts `disambiguation` shape integrity
- *   - `scripts/intent-resolution-eval.ts --surface=directory` (ADR-229 PR-3)
- *   - the Phase 4 description rewrites — `Use when the user asks` blocks
- *     pull question + synonym strings from here
- *
- * The `AtlasEntry` type is inline-duplicated rather than imported from a
- * shared package, mirroring ADR-228's choice (Open Question 3 default —
- * extract to `packages/mcp-atlas-types/` only if a fourth MCP surface
- * lands or the type drift becomes painful).
- *
- * Two shape extensions vs the creator and operator atlases (per ADR-229
- * Decision 4):
- *
- *   1. `clean_empty_state?: { message; suggest_query_shape }` — public-
- *      surface analog of `fallback_when_empty`. The directory has no
- *      internal action to nudge toward (the empty state IS the final
- *      answer for the anonymous user); this field carries the prescribed
- *      empty-state copy plus a query-shape hint for the calling LLM.
- *
- *   2. `disambiguation?: { ambiguous_terms[]; resolver_tool; resolver_intent }` —
- *      first-class concern on the public surface (creator/operator MCPs
- *      have a calling-context that narrows the search; the public
- *      directory hits "Bowie", "Sade", "Madonna", "Lover Boy" constantly
- *      and must declare an explicit resolver step).
- *
- * `clean_empty_state` and `fallback_when_empty` are mutually exclusive on
- * a single entry — Rule 11F enforces this at lint time.
- *
- * The public atlas omits `natural_domain` (creator-side binds to
- * `discovery.ts` CATEGORIES; the directory MCP has no equivalent
- * taxonomy — the discovery surface is search and lookup, not category-
- * faceted browse). It also omits `available_when` (the operator atlas's
- * forward-compat hook for unshipped sections; the directory has no
- * deferred-section concept).
- */
-export interface AtlasFallback {
-    message: string;
-    next_tool: string;
-}
-export interface AtlasCleanEmptyState {
-    /**
-     * Atlas-prescribed copy for the empty-state response. The calling LLM
-     * may render in its own voice; the suggested-query-shape hint is the
-     * load-bearing part.
-     */
-    message: string;
-    /**
-     * Free-text hint for how to refine the query, interpreted by the LLM
-     * as guidance (not rendered verbatim). Example:
-     * `"title + writer | title + year | ISWC if known"`.
-     */
-    suggest_query_shape: string;
-}
-export interface AtlasDisambiguation {
-    /**
-     * Names known to be ambiguous in the music-metadata domain (multiple
-     * persons, artist projects, or works with the same string). v1 ships
-     * a static list; v2 (deferred per ADR-229 § Risks #3) could resolve
-     * dynamically against the index's name-collision frequency.
-     */
-    ambiguous_terms: string[];
-    /**
-     * The directory tool the agent should call FIRST to surface candidate
-     * entities for the user to disambiguate before committing to the
-     * lookup tool in `resolves_to`.
-     */
-    resolver_tool: string;
-    /**
-     * Free-text guidance for the LLM on how to run the resolver step.
-     * Example: `"Call directory_lookup_person first to surface candidates;
-     * ask which one before calling directory_list_works."`
-     */
-    resolver_intent: string;
-}
-export type AtlasResolution = {
-    kind: "tool";
-    name: string;
-    default_args?: Record<string, unknown>;
-} | {
-    kind: "prompt";
-    name: string;
-};
-export interface AtlasEntry {
-    question: string;
-    synonyms: string[];
-    resolves_to: AtlasResolution;
-    /** Mutually exclusive with `clean_empty_state` (lint-enforced). */
-    fallback_when_empty?: AtlasFallback;
-    /** ADR-229 Decision 4 — public-surface empty-state contract. */
-    clean_empty_state?: AtlasCleanEmptyState;
-    /** ADR-229 Decision 4 — public-surface name-collision contract. */
-    disambiguation?: AtlasDisambiguation;
-}
-/**
- * Names known-ambiguous in the music-metadata domain — multiple persons
- * sharing a stage name, or artist project names that collide with
- * person names. Seed list per ADR-229 § Open Q2 (case-insensitive — the
- * lint and the resolver normalise on lowercase).
- *
- * Grow this list as Phase 5 eval data surfaces real collisions the
- * static seed misses. Do not prune without eval evidence — the cost of
- * missing a real collision (wrong-tool routing on a public-facing
- * surface) is higher than the cost of an extra resolver call.
- */
-export declare const AMBIGUOUS_NAMES: string[];
-export declare const PUBLIC_ATLAS: AtlasEntry[];
-//# sourceMappingURL=public-question-atlas.d.ts.map

package/dist/prompts/public-question-atlas.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"public-question-atlas.d.ts","sourceRoot":"","sources":["../../src/prompts/public-question-atlas.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgDG;AAEH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;CACnB;AAED,MAAM,WAAW,oBAAoB;IACnC;;;;OAIG;IACH,OAAO,EAAE,MAAM,CAAC;IAChB;;;;OAIG;IACH,mBAAmB,EAAE,MAAM,CAAC;CAC7B;AAED,MAAM,WAAW,mBAAmB;IAClC;;;;;OAKG;IACH,eAAe,EAAE,MAAM,EAAE,CAAC;IAC1B;;;;OAIG;IACH,aAAa,EAAE,MAAM,CAAC;IACtB;;;;OAIG;IACH,eAAe,EAAE,MAAM,CAAC;CACzB;AAED,MAAM,MAAM,eAAe,GACvB;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAC;IAAC,YAAY,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAA;CAAE,GACtE;IAAE,IAAI,EAAE,QAAQ,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAAC;AAErC,MAAM,WAAW,UAAU;IACzB,QAAQ,EAAE,MAAM,CAAC;IACjB,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,WAAW,EAAE,eAAe,CAAC;IAC7B,mEAAmE;IACnE,mBAAmB,CAAC,EAAE,aAAa,CAAC;IACpC,gEAAgE;IAChE,iBAAiB,CAAC,EAAE,oBAAoB,CAAC;IACzC,mEAAmE;IACnE,cAAc,CAAC,EAAE,mBAAmB,CAAC;CACtC;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,eAAe,EAAE,MAAM,EAWnC,CAAC;AAEF,eAAO,MAAM,YAAY,EAAE,UAAU,EAqZpC,CAAC"}