Skip to main content
Glama

CWR validation (CWR 2.1 or 2.2 file check)

validate_cwr
Read-onlyIdempotent

CWR validation: checks the text of a CWR 2.1 or 2.2 (Common Works Registration) file, against the version it declares. CWR registers songs with societies such as The MLC, PRS for Music / ICE, SACEM or CMRRA. Returns whether the file is valid, error and warning counts, and each issue with its line, rule, plain-language explanation and how to fix it. Pass the file content as ASCII text, up to 256 KB; larger files can be uploaded at https://trackforge.studio/cwr-tool. Validation does not guarantee acceptance by a society. The file is not stored.

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": {
      "cwr_text": "<cwr_text>"
    },
    "name": "validate_cwr"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwr_textYesThe full CWR file content (ASCII text, HDR to TRL).
filenameNoOptional original filename, e.g. CW260001TF_000.V21. A society receiver code in the name selects that society's rules.
recipient_profileNoWhich society's rules to apply; cisac_base when unsure.cisac_base

Output Schema

NameRequiredDescriptionDefault
issuesYes
storedNo
is_validYes
error_countYes
full_reportYes
issues_totalYes
record_countYes
spec_versionYes
warning_countYes
issues_truncatedYes
recipient_profileYes
status_dimensionsNo
transaction_countYes
recipient_resolutionYes
line_endings_convertedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / recipient_profile / enum
      Previous value: -[
      -  "cisac_base",
      -  "mlc",
      -  "cmrra",
      -  "alltrack_worldwide",
      -  "alltrack_us_only",
      -  "capasso_africa",
      -  "abramus",
      -  "ice",
      -  "sacem",
      -  "siae",
      -  "sgae",
      -  "prs"
      -]New value: +[
      +  "cisac_base",
      +  "mlc",
      +  "cmrra",
      +  "alltrack_worldwide",
      +  "alltrack_us_only",
      +  "capasso_africa",
      +  "capasso_english_portuguese",
      +  "abramus",
      +  "ice",
      +  "sacem",
      +  "siae",
      +  "sgae",
      +  "prs"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / recipient_profile / enum
      Previous value: -[
      -  "cisac_base",
      -  "mlc",
      -  "cmrra",
      -  "alltrack_worldwide",
      -  "alltrack_us_only",
      -  "capasso_africa",
      -  "ice",
      -  "sacem",
      -  "siae",
      -  "sgae",
      -  "prs"
      -]New value: +[
      +  "cisac_base",
      +  "mlc",
      +  "cmrra",
      +  "alltrack_worldwide",
      +  "alltrack_us_only",
      +  "capasso_africa",
      +  "abramus",
      +  "ice",
      +  "sacem",
      +  "siae",
      +  "sgae",
      +  "prs"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the file is not stored, validation does not guarantee society acceptance, and it enumerates error/warning counts and per-issue fix guidance.

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?

Front-loaded with the core purpose, then return shape, then limits and caveats. Slightly dense but every sentence carries information an agent would otherwise have to guess.

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

Completeness4/5

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

Return values are covered by the output schema and safety by annotations, so the description's remaining burden is size/format limits, storage behavior, and expectations — all present. Only a note on how warnings differ from validity is absent.

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%, so the schema already documents all three parameters including the society-code filename trick and the recipient_profile enum. The description only restates the ASCII/size constraint, adding little new meaning.

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?

States a specific verb and resource ('checks the text of a CWR 2.1 or 2.2 file, against the version it declares') plus the domain context (CWR registers songs with societies). The resource domain is far enough from siblings like check_catalogue and lookup_recording that no agent could confuse them.

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

Usage Guidelines4/5

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

Gives clear invocation context (ASCII text, up to 256 KB) and an explicit alternative route for oversized files via the upload URL. It does not state when to prefer this over the sibling tools, but the input type makes that largely self-evident.

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