Skip to main content
Glama

query_provenance

Read-only

Free registry and published-pack lookup for an assetId / seal / QR token; use for discovery, not proof of authenticity. Reads matching rows from the canonical auth_seals registry when public Supabase configuration is available, and also resolves published packs. A registry match means registered only; it does not verify a signature or prove a physical item is genuine. Use verify_attestation for a published v0.1 JWS; verify_record is the separate reference-protocol verifier.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assetId": "<assetId>"
    },
    "name": "query_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesSeal, serial, or QR token identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the bar is lower; the description still adds real context: it reads from the canonical auth_seals registry, depends on public Supabase configuration being available, also resolves published packs, and clarifies that a match means 'registered only' rather than a verified signature. It stops short of saying what happens when the Supabase config is absent (error vs. empty result) or what a match payload contains, which keeps it below a 5.

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?

Three front-loaded sentences that put the lookup scope first and the alternatives last; almost every clause earns its place. The only waste is mild repetition between 'not proof of authenticity' and the later 'does not verify a signature or prove a physical item is genuine', which say largely the same thing twice.

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 one-parameter, read-only, open-world lookup with no output schema, the description covers purpose, trust semantics, data source, and sibling routing. The remaining gap is the failure mode when public Supabase configuration is unavailable and a hint at what a resolution returns, but nothing essential to correct invocation is 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?

Only one parameter exists, and the schema already documents it at 100% coverage ('Seal, serial, or QR token identifier'). The description's phrase 'assetId / seal / QR token' merely restates that, adding no format, normalization, or ambiguity guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Free registry and published-pack lookup for an assetId / seal / QR token') and immediately scopes it ('use for discovery, not proof of authenticity'). It explicitly separates itself from verify_attestation and verify_record, so an agent can choose without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the use case (discovery of registry entries and published packs) and the exclusion (not proof of authenticity), then routes to the two concrete alternatives: verify_attestation for a published v0.1 JWS and verify_record for the reference-protocol verifier. When-to-use and when-not-to-use are both explicit.

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.