Skip to main content
Glama

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

Art validation-resources directory

get_art_validators_directory
Read-only

Art validation-resources directory. The Ni Biashara art shelf's validation-resources directory: who authenticates what — artist foundations and catalogue-raisonné authorities, forensic labs, stolen-art registers, appraisal bodies, fine-art insurers and AI-detection services — with published prices where they exist and dissolved authorities flagged. $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": "get_art_validators_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
validator_typeNovalidator type: artist_foundation, forensic_lab, register, research_resource, appraisal_body, insurer or detection_service (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive, so the safety bar is low; the description adds genuinely new behavior: published prices included, dissolved authorities flagged, a $0.25 USDC-on-Base x402 flow, and the explicit clarification that calling the tool is free with payment occurring at the returned URL. That x402 explanation is the kind of context annotations cannot convey.

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 resource identity is front-loaded, then the contents, then the payment mechanics. The em-dash enumeration is dense but informative; the closing pricing trio ($0.25 USDC on Base / x402 URL / free to call) is slightly repetitive in restating payment twice, costing a small amount of tightness.

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?

For a one-optional-param read tool with no output schema, the description covers what the directory contains, what extra data is surfaced (prices, dissolved-authority flags), and, crucially, what the tool actually returns (an x402 URL, not the data itself) along with the 402 → PAYMENT-SIGNATURE → delivery sequence. An agent can call it correctly without further information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented in-schema, so the baseline is 3. The description earns a notch above it by enumerating the resource categories (artist foundations, forensic labs, registers, appraisal bodies, insurers, detection services), which gives the agent a concrete sense of what the validator_type filter selects among.

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 resource (a validation-resources directory for art authentication) and enumerates its contents — foundations, catalogue-raisonné authorities, forensic labs, registers, appraisal bodies, insurers, detection services. This distinguishes it from the provenance-checking siblings (check_art_provenance, get_art_provenance_dossier) without naming them explicitly.

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: call this to find out who authenticates what. The description also clarifies the payment flow (free to call, pay on the returned URL), which is practical guidance. However, it never states when to prefer this over the provenance/dossier siblings, leaving the choice 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