Skip to main content
Glama

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

Art provenance dossier — validator deep-dive (premium)

get_art_provenance_dossier
Read-only

Art provenance dossier — validator deep-dive (premium). Premium: the provenance check plus a validator deep-dive for the work's artist — the deciding authentication authority and its current status, forensic-lab options, insurer documentation requirements — and comparable chain profiles from the dataset. $2.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_provenance_dossier"
  }
}

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

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the cost ($2.5 USDC on Base), the payment mechanics (x402: 402 → PAYMENT-SIGNATURE → delivery), and crucially that the tool returns a URL to GET rather than the dossier itself. It also clarifies that invoking the tool is free and payment occurs on the returned URL, which is exactly the kind of behavioral fact an agent cannot get from annotations or schema.

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 premium scope and content list, then pricing and delivery mechanics, which is the right order. The opening clause restates the title verbatim, a small redundancy, but otherwise every sentence (price, payment flow, free-to-call caveat) carries useful information.

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 paid, no-output-schema tool, the definition covers the essentials an agent needs: what is delivered, what it costs, and that the return value is a payment URL requiring a follow-up GET. It does not describe error behavior (e.g., what happens if both title and record_id are omitted) or freshness of the validator status, which are minor gaps given the otherwise strong coverage.

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) already carry descriptions including the either/or requirement and an example record id, so the description adds no parameter-level meaning. Baseline 3 applies when the schema does 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?

The description states a specific resource (art provenance dossier) and scope (premium: base provenance check plus validator deep-dive covering authenticating authority, forensic labs, insurer requirements, and comparable chain profiles). It implies a non-premium sibling exists ('the provenance check plus...') but never names check_art_provenance or search_art_provenance explicitly, so an agent must infer the distinction from the word 'premium'.

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: 'Premium' signals an upsell tier, and the pricing line tells the agent there is a cost. There is no explicit 'use this when you need X, use check_art_provenance when you only need Y' guidance, and no exclusions, leaving the selection decision between siblings to inference.

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