Skip to main content
Glama

trace music culture inheritance

trace_music_culture_inheritance
Read-onlyIdempotent

Read inheritance records that name the authenticated agent as parent or child. Requires an authenticated session and current music_retrieval grant; results distinguish an inherited finding from personal listening. It creates no transfer and no listening receipt. Use inspect_listening_receipt for your own listening status; never treat inherited provenance as evidence that this agent heard the audio.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trace_music_culture_inheritance"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoThis optional field is present in the shared music-tool schema but is not read by this operation; omit it.
receipt_idNoThis optional field is present in the shared music-tool schema but is not read by this operation; omit it.
idempotency_keyNoThis optional field is present in the shared music-tool schema but is not read by this operation; omit it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / idempotency_key / description
      Added value: +"This optional field is present in the shared music-tool schema but is not read by this operation; omit it."
    • addedInput schema / properties / query / description
      Added value: +"This optional field is present in the shared music-tool schema but is not read by this operation; omit it."
    • addedInput schema / properties / receipt_id / description
      Added value: +"This optional field is present in the shared music-tool schema but is not read by this operation; omit it."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already supply the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description goes further: it states the auth prerequisite ('authenticated session and current music_retrieval grant') and explicitly disclaims side effects ('creates no transfer and no listening receipt'). That is exactly the kind of gate and side-effect information annotations cannot express.

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?

Four short sentences, front-loaded: purpose, prerequisites, side-effect disclaimer, then routing caveat. Every sentence carries distinct information and nothing repeats the name or schema.

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 read-only tool with full annotation coverage and no output schema, this covers purpose, auth gate, side-effect profile, result semantics ('distinguish an inherited finding from personal listening') and routing. The only modest gap is that the return structure is gestured at rather than described, which matters slightly more because no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, and all three parameters are self-documenting as no-ops ('not read by this operation; omit it'), so effectively zero parameters matter here. The description correctly adds no redundant parameter prose, matching the 0-param baseline.

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 ('Read inheritance records') plus the exact scope ('that name the authenticated agent as parent or child'), which no other sibling covers. The distinction from the loosely related inspect_listening_receipt is drawn explicitly, so an agent can route without opening either schema.

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?

Names a concrete alternative (inspect_listening_receipt) and the condition that selects it ('for your own listening status'), and adds a when-not caveat about misreading inherited provenance as first-hand listening. It is clear context, but does not enumerate any other adjacent siblings or exclusions.

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