Skip to main content
Glama

Catalogue registration check: up to 50 recordings against The MLC

check_catalogue
Read-onlyIdempotent

Catalogue registration check (batch ISRC lookup): checks up to 50 recordings at once against The MLC's bulk data (US mechanical royalties), and a larger catalogue in several calls. Returns each recording's verdict (registered, partial, nobody, conflict, missing_from_bulk, unknown) with its confidence, MLC song code and any unclaimed share, plus a summary counting each verdict, the next step for each verdict found, and the as_of date of the MLC snapshot. Each row also lists the ISWCs and writers of the works MusicBrainz links to the recording. Invalid ISRCs are listed and skipped. It finds recordings whose music royalties may be unmatched or unclaimed. Findings from registration data, not legal advice or a statement of song ownership.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "isrcs": "<isrcs>"
    },
    "name": "check_catalogue"
  }
}

Input Schema

NameRequiredDescriptionDefault
isrcsYesISRCs, 12 characters, e.g. USIR20400274 (hyphens and spaces allowed). At most 50; split larger catalogues into several calls.

Output Schema

NameRequiredDescriptionDefault
itemsYes
summaryYes
mlc_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / CatalogueSummary / properties / not_read
      Added value: +{
      +  "default": [
      +    "PRS for Music",
      +    "MCPS"
      +  ],
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Not Read",
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • changedOutput schema / $defs / VerdictState / description
      Previous value: -"What the registration data shows for a recording, in one word.\n\nPrecedence when several apply: unknown > conflict > nobody > partial >\nregistered (``app/services/isrc/verdict.py``). Only a snapshot that was\nread can produce ``nobody``; an unreadable copy is ``unknown``."New value: +"What the registration data shows for a recording, in one word.\n\nPrecedence when several apply: unknown > missing_from_bulk > conflict >\nnobody > partial > registered (``app/services/isrc/verdict.py``). Only a\nsnapshot that was read can produce ``nobody``; an unreadable copy is\n``unknown``. ``missing_from_bulk``: an earlier copy of The MLC's bulk data\nlisted publishers on the work, or linked the recording to a work, and this\ncopy does not; the bulk data has dropped claims that are still live, so\nthe gap is not evidence that a share is unclaimed or no work is linked."
    • changedOutput schema / $defs / VerdictState / enum
      Previous value: -[
      -  "registered",
      -  "partial",
      -  "nobody",
      -  "conflict",
      -  "unknown"
      -]New value: +[
      +  "registered",
      +  "partial",
      +  "nobody",
      +  "conflict",
      +  "missing_from_bulk",
      +  "unknown"
      +]
  3. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, and the description adds meaningful context: verdict categories, summary counts, next-step guidance, the as_of snapshot date, and skipped invalid ISRCs. It also clearly disclaims legal advice and ownership conclusions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and tightly written, though it is dense and repeats the 50-recording limit. Most content earns its place, but some output detail overlaps with the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations, complete input schema, and existing output schema, the description supplies enough detail about verdicts, summary behavior, invalid ISRC handling, and snapshot timing for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the schema already documents ISRC format, allowed hyphens/spaces, and the 50-item maximum. The description reinforces batching and notes that invalid ISRCs are listed and skipped, but adds little syntax or meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: a catalogue registration check via batch ISRC lookup against The MLC's bulk data. The batch scope and 50-recording limit make it distinguishable from a single-recording lookup even without naming a sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies when to use the tool, namely batch checking, and advises splitting larger catalogues across calls. However, it gives no explicit exclusions or comparison to siblings such as lookup_recording or request_full_report.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources