Skip to main content
Glama

ISRC music copyright proof, Bitcoin timestamp (ProofProfile, paid)

verify_artist

Read-only

PAID, from one cent in USDC by x402; the first reply is the price and nothing is charged until the AI agent signs a payment. Evidence that an artist, by ProofProfile registry id, exists in the frozen corpus: the closure manifest entry, the record hash, the Bitcoin-anchored proof and the CopyrightChains block. Returned with a capsule that verifies offline and a receipt of this call anchored in Bitcoin.

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": {
      "artist_id": "<artist_id>"
    },
    "name": "verify_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoOptional: what the AI agent is about to do, in its own words. Bound into the anchored receipt as part of the call, so the receipt shows why it was made.
artist_idYesregistry artist id, for example 21410
referenceNoOptional: the AI agent's own reference for the action, such as an order id or sha256:<hash> of its document. Bound into the anchored receipt as part of the call.
declaredValueUsdNoThe stakes in US dollars the AI agent is acting on. They set the price band (one cent under $100, ten cents from $100, one dollar from $10,000); undeclared stakes are priced at one cent. The declared figure is part of the call that the receipt anchors in Bitcoin, so the receipt shows it. No money other than the price moves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the commercial model in detail: paid from one cent in USDC via x402, the first reply is only the price, and nothing is charged until the agent signs a payment. It also explains that the result comes with an offline-verifiable capsule and a Bitcoin-anchored receipt of the call, which is exactly the behavioral context an agent needs before invoking a paid, non-idempotent tool.

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?

Two dense sentences, both carrying real information, with the payment condition front-loaded so an agent sees the cost implication before anything else. The phrasing is somewhat compressed ('Evidence that an artist... exists') and the purpose arrives after the billing detail, but nothing is wasted.

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?

There is no output schema, and the description compensates by listing the returned artifacts (manifest entry, record hash, anchored proof, CopyrightChains block, offline capsule, receipt). For a four-parameter paid verification tool, an agent has everything needed to decide and call 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%, so the schema already documents all four parameters, including the declaredValueUsd price bands. The description reinforces the artist_id as a ProofProfile registry id and ties pricing to 'one cent' and the anchored receipt, but adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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

Purpose4/5

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

The description names a specific verb and resource: evidence that an artist, by ProofProfile registry id, exists in the frozen corpus, and enumerates exactly what evidence is returned (closure manifest entry, record hash, Bitcoin-anchored proof, CopyrightChains block). The resource noun (artist) separates it from the verify_recording/find_recording siblings without needing to name them, though no explicit sibling routing is given.

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?

Usage is implied rather than stated: an agent infers it should call this when it needs proof of an artist's existence in the frozen corpus. There is no explicit when-to-use, when-not-to-use, or named alternative versus verify_recording, and no precondition guidance (e.g., needing a registry id in hand first).

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