Skip to main content
Glama

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

Art provenance search

search_art_provenance
Read-only

Art provenance search. Filtered search over the Ni Biashara art provenance shelf: museum collection records with structured provenance chains, continuity grades and documented transfer counts. Filter by text, artist, holding institution, medium or a transfer-count floor. Prices are never estimated — the price layer is named as a gap per record. $0.25 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": "search_art_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNofree text over work title and artist (optional)
limitNomax records to return (optional, default 25, max 60)
artistNoartist name text, e.g. Peter Paul Rubens (optional)
mediumNomedium text, e.g. Oil on canvas (optional)
offsetNorecords to skip (optional, default 0)
institutionNoholding institution name text, e.g. Cleveland Museum of Art (optional)
min_transfersNoonly records with at least this many documented transfers (optional)

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 readOnlyHint/openWorldHint/destructiveHint, it discloses the non-obvious economics and flow: $0.25 USDC on Base, the tool call itself is free, payment happens against a returned x402 URL following 402 → PAYMENT-SIGNATURE → delivery. It also discloses a data-quality trait an agent must know — prices are never estimated and the price layer is explicitly a named gap per record.

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?

Dense and front-loaded: shelf, contents, filters, price caveat, then payment mechanics in a single traversal. The opening "Art provenance search." duplicates the tool name/title and earns little, and the payment sentence is telegraphic enough to require a second read, but nothing else is wasted.

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?

With no output schema, the description carries the return burden and does describe the record shape (provenance chains, continuity grades, transfer counts) plus the actual response being an x402 URL rather than records. Pagination defaults live in the schema, so the omission of paging behavior from the description is minor.

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%, so all seven parameters are already documented in the schema, and the description adds no format, syntax, or interplay details (e.g. how q combines with artist/institution). It only restates the filter dimensions and gives the transfer-count floor meaning via "documented transfer counts." Baseline 3 applies.

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 verb and resource ("Filtered search over the Ni Biashara art provenance shelf") and enumerates what the records contain: provenance chains, continuity grades, documented transfer counts. It does not name which sibling to use instead (check_art_provenance, get_art_provenance_dossier), so differentiation from those alternatives is left to the agent.

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 lists the filter dimensions available, which implies the tool's role as a discovery/browse step, but never states when to use it versus check_art_provenance or get_art_provenance_dossier, nor any prerequisites or exclusions. Usage is implied rather than prescribed.

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