Skip to main content
Glama

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

Art provenance check — one work (premium)

check_art_provenance
Read-only

Art provenance check — one work (premium). Premium: one work from the Ni Biashara art provenance shelf — its full provenance chain as published, continuity grade, documented transfer count, the validation routes for its artist, and a stolen-art register clearance checklist. No price is estimated for the work. $1 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": "check_art_provenance"
  }
}

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?

Annotations already cover read-only/non-destructive/open-world, but the description goes well beyond them by disclosing the commercial and protocol behavior: $1 USDC on Base, calling the tool is free, and delivery requires GET on the returned x402 URL through 402 → PAYMENT-SIGNATURE. It also states a scope exclusion (no price estimate), which prevents an agent from misusing the result. This is exactly the non-obvious, non-structured context the agent needs before invoking.

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 payload is front-loaded in the first sentence, with cost and delivery protocol following. There is mild redundancy — 'Premium:' is restated, and 'Free to call this tool; payment happens on the URL' repeats the x402 sentence's point — but no filler or vague phrasing.

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 two-optional-parameter read tool with no output schema, the description says what comes back and how to pay for it, which is the hard part. It omits error/ambiguity handling for a title with multiple matches and does not say whether a failed check is still billed, both minor relative to the delivery detail supplied.

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 two parameters (title, record_id) and their 'this or title required' constraint are already fully documented in the schema. The description adds no parameter-level meaning, such as fuzzy-match tolerance or how to resolve a title that returns multiple works. Baseline 3 is appropriate when the schema carries the full burden.

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 ('art provenance check'), scopes it to one work, and enumerates exactly what the answer contains: provenance chain, continuity grade, transfer count, artist validation routes, and a stolen-art clearance checklist. It also draws a useful boundary ('no price is estimated'). It never names or contrasts a sibling such as get_art_provenance_dossier, so an agent must infer from scope alone which tool to pick.

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 only implied: ask for one work when you want its documented chain and clearance status. There is no explicit 'use this instead of X' routing, no statement about what to do when a title is ambiguous, and no guidance on when the free lookup is insufficient and a dossier is needed. Payment mechanics are explained, but tool-selection guidance is not.

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