Skip to main content
Glama

Verify an asset

verify
Read-onlyIdempotent

Use when someone shows you a proof, certificate or token and you want to check it before relying on it, or you need the facts about any asset on Bitcoin. Free, no API key. For agent names, verify_agent gives a clearer identity verdict. Looks up any token on Bitcoin by asset name (e.g. A12044707814007245827 or GAMESOFTRUMP). For proofs made on Prove It Onchain it returns the claim, the pass/fail checks (exists, supply is 1, locked, claim record reachable and matching its on-chain hash), owner, creation tx, the certificate URL and the record URL. For other assets it returns their facts (owner, supply, divisibility, lock status) without proof checks. Read-only.

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": {
      "asset": "<asset>"
    },
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset name, numeric (A…) or named.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description adds context annotations cannot carry: no API key or cost, and the different response shapes for Prove It Onchain proofs (claim, pass/fail checks, owner, tx, certificate and record URLs) versus plain assets (owner, supply, divisibility, lock status). The only redundancy is restating 'Read-only', which the annotations already cover.

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 usage trigger and alternative routing, then progressively adds lookup format and return details. It runs long, and the trailing 'Read-only' duplicates the annotation, but every other clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description compensates by enumerating what both response branches return, and it covers cost, auth (none), accepted input formats and the relevant sibling. Nothing an agent needs in order to call this correctly appears to be missing.

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 already 100% for the single 'asset' parameter, so the baseline is 3; the description earns above that by giving concrete accepted formats ('A12044707814007245827 or GAMESOFTRUMP'), which make the numeric-vs-named convention tangible rather than abstract.

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 names a specific verb-and-resource pair (verify a proof/certificate/token or look up facts about an asset on Bitcoin) and explicitly distinguishes itself from the sibling verify_agent, which handles agent names. An agent can route between verify and verify_agent from the description alone.

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 gives an explicit trigger scenario ('someone shows you a proof, certificate or token and you want to check it before relying on it'), a second use case (need facts about any asset on Bitcoin), and names the alternative tool with the condition that selects it ('For agent names, verify_agent gives a clearer identity verdict').

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.