Skip to main content
Glama

Taifoon coordination layer

Prove a chain fact

taifoon_prove
Read-onlyIdempotent

Proves blocks, transactions, logs and transfers under the Taifoon superroot. For reading chain data without a proof use taifoon_chain. Actions: tx — one transaction inside the superroot (chain, tx); item — anything the superroot commits, by kind: tx, log, receipt, state; block — a block under the superroot (proof.verify.v5); superroot — the current superroot and the chains it includes; transfer — attest a cross-chain CCTP transfer; finality — what a V5 finality type id means.

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": "taifoon_prove"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNokey (actions: item)
kindNokind (actions: item)
seqsNoseqs (actions: item)
actionNowhat to do (default tx): tx | item | block | superroot | transfer | finalitytx
blocksNoblocks (actions: item)
api_keyNoapi key (actions: item)
tx_hashNotx hash (actions: tx, item, transfer)
type_idNotype id (actions: finality)
chain_idNoany chain the layer reads (GET /v1/rpc): 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 999, 99901, 2741, 196, 143, 100; another chain answers 404 chain_not_read (actions: tx, item, block, transfer)
protocolNoprotocol (actions: item)
log_indexNolog index (actions: item)
block_numberNoBlock number on that chain (actions: block)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain_id / description
      Previous value: -"any chain the layer reads (GET /v1/rpc): 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 2741, 196, 143, 100; another chain answers 404 chain_not_read (actions: tx, item, block, transfer)"New value: +"any chain the layer reads (GET /v1/rpc): 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 999, 99901, 2741, 196, 143, 100; another chain answers 404 chain_not_read (actions: tx, item, block, transfer)"
  2. Changed13 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "default": "tx",
      +  "description": "what to do (default tx): tx | item | block | superroot | transfer | finality",
      +  "enum": [
      +    "tx",
      +    "item",
      +    "block",
      +    "superroot",
      +    "transfer",
      +    "finality"
      +  ],
      +  "examples": [
      +    "tx"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / api_key / description
      Added value: +"api key (actions: item)"
    • addedInput schema / properties / block_number
      Added value: +{
      +  "description": "Block number on that chain (actions: block)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / blocks / description
      Added value: +"blocks (actions: item)"
    • addedInput schema / properties / chain_id / description
      Added value: +"any chain the layer reads (GET /v1/rpc): 8453, 5042, 1, 56, 43114, 42161, 137, 10, 4663, 42220, 36927, 3692781, 2741, 196, 143, 100; another chain answers 404 chain_not_read (actions: tx, item, block, transfer)"
    • addedInput schema / properties / key / description
      Added value: +"key (actions: item)"
    • addedInput schema / properties / kind / description
      Added value: +"kind (actions: item)"
    • addedInput schema / properties / log_index / description
      Added value: +"log index (actions: item)"
    • addedInput schema / properties / protocol / description
      Added value: +"protocol (actions: item)"
    • addedInput schema / properties / seqs / description
      Added value: +"seqs (actions: item)"
    • addedInput schema / properties / tx_hash / description
      Added value: +"tx hash (actions: tx, item, transfer)"
    • addedInput schema / properties / type_id
      Added value: +{
      +  "description": "type id (actions: finality)",
      +  "maximum": 15,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "kind"
      -]
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds some behavioral context — the superroot scope, the proof.verify.v5 binding for block proofs, and V5 finality type-id semantics — but does not discuss error modes, auth requirements, or the shape of a returned proof.

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 routing sentence is front-loaded and the action glossary is compact, one clause per action. It is slightly redundant with the schema's own action/applicability descriptions, so a small amount of text does not earn extra value, but nothing is padded or meandering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, six-action tool with no output schema, the definition covers purpose and action selection but says nothing about what a proof response contains or how to interpret verification artifacts. Given there is no output schema to fall back on, a sentence on return shape would materially improve completeness.

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% and every parameter already carries an '(actions: ...)' applicability hint, so the schema does the heavy lifting. The description's per-action sentences largely mirror that structured information (e.g., 'block — a block under the superroot') rather than adding new meaning such as value ranges, defaults, or how seqs/block arrays compose.

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+resource ('Proves blocks, transactions, logs and transfers under the Taifoon superroot') and then enumerates each action with its own meaning (tx, item, block, superroot, transfer, finality). It also names the sibling taifoon_chain as the non-proof reader, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent: 'For reading chain data without a proof use taifoon_chain,' which is a clear when-to-use-this-vs-alternative statement. It also ties actions to their purpose (e.g., transfer attests a cross-chain CCTP transfer, finality decodes a V5 type id), though it does not state exclusions or prerequisites such as when an action would fail.

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