Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Art provenance dossier, live tier (premium)

get_art_dossier_live
Read-only

Art provenance dossier, live tier (premium). Premium live tier: the provenance dossier re-checked at call time. On the current snapshot build the live re-check cannot complete, so the call serves the audited-snapshot dossier and names the degradation in the payload — no live freshness is claimed that was not performed. $5 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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": "get_art_dossier_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNowork title, exact or close match (this or record_id required)
record_idNorecord id from art-search, e.g. art-cma-1959.190 (this or title required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-destructive), the description discloses the degradation of the live re-check, that the audited-snapshot dossier is served instead, that the degradation is named in the payload, the $5 USDC on Base cost, and the 402 → PAYMENT-SIGNATURE → delivery flow. These are exactly the behavioral facts an agent needs and that structured fields do not carry.

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 operational substance (degradation, price, payment flow) comes early and every clause carries weight. The opening repeats the title verbatim before restating 'Premium live tier', which is minor redundancy but the only real waste.

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?

With no output schema, the description still explains what is returned (an x402 URL to GET) and the handshake sequence, plus the material caveat about degraded freshness and the payload disclosure. Nothing an agent needs to decide to call, or to act on the result, appears missing.

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 both parameters (title, record_id) are already documented with their either/or requirement in the schema. The description adds no additional syntax, matching behavior, or fallback rules for these inputs, so the schema does all the work.

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?

States a specific resource and scope: 'the provenance dossier re-checked at call time', which separates it from a plain snapshot dossier. The 'live tier (premium)' framing distinguishes it from the non-live sibling by implication, but no sibling is named explicitly, so differentiation is not fully pinned down.

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?

The description tells the agent it is free to call and that payment occurs on the returned URL, which is operative guidance. It also warns that the live re-check currently cannot complete, effectively steering away from expecting freshness, but it never names an alternative or states plainly when to prefer get_art_provenance_dossier instead.

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