MusicCheck: copyright screening

Get a screening result

get_screening

Read-onlyIdempotent

Fetch the status and result of one screening. When status is COMPLETED, returns every window where a commercial recording was detected, with timestamps and the matched title/artist, plus a plain-language verdict on whether the file is safe to publish.

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": {
      "uuid": "<uuid>"
    },
    "name": "get_screening"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes	The screening uuid (or report_id without the MC- prefix)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description carries the return-value burden and does so well: it discloses that results are conditional on status and enumerates windows, timestamps, matched title/artist, and a publish-safety verdict. It stops short of describing the non-COMPLETED states or error behavior.

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

Conciseness5/5

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

Two sentences, zero filler, front-loaded with the action and scope before the return-shape detail. Every clause earns its place and nothing is repeated from structured fields.

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?

For a one-parameter, no-output-schema tool the description covers the payload an agent would otherwise lack (fields, conditionality, verdict). It is only slightly incomplete in not sketching what a non-COMPLETED or failed response looks like.

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 description coverage is 100% and the single uuid parameter is already documented there, including the 'report_id without MC- prefix' note. The description adds no syntax, format, or lookup semantics beyond the schema, so the baseline 3 applies.

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 (Fetch) and resource (the status and result of one screening), with the scope word 'one' distinguishing it from the sibling list_screenings and from screen_audio which creates screenings. An agent knows immediately this is a single-item retrieval keyed by uuid.

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

Usage Guidelines2/5

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

The description never says when to reach for this tool versus list_screenings, screen_audio, or verify_report, and states no prerequisites (e.g., that a screening must already exist or how a uuid is obtained). The 'When status is COMPLETED' clause is behavioral, not usage routing.

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

All MusicCheck: copyright screening tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?