Skip to main content
Glama

Proof status

get_proof_status
Read-onlyIdempotent

Use after broadcast to see whether your proof has confirmed. Free. Status of a proof by record_id: awaiting_signature, expired, pending, or confirmed, with txid, asset, confirmations and links.

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": {
      "record_id": "<record_id>"
    },
    "name": "get_proof_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYesrecord_id returned by create_proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld behavior, so the bar is lower; the description still adds real value by disclosing the status lifecycle (awaiting_signature, expired, pending, confirmed), the returned fields (txid, asset, confirmations, links) and that the call is free. It does not discuss latency of status transitions or error behavior for unknown record_ids.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with zero filler; the usage trigger leads and the expected output follows. Every clause carries information an agent would otherwise lack.

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 simple one-parameter read tool with no output schema, the description adequately compensates by listing the return fields and status values. Minor gaps remain around error cases and how quickly status changes, but nothing essential to invoking it 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?

Schema coverage is 100% and the single record_id parameter is fully documented as 'returned by create_proof', so the description adds no further parameter meaning beyond the schema. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('Status of a proof by record_id') and enumerates the possible statuses and returned fields, so an agent knows exactly what it retrieves. It is clearly distinguishable from siblings like broadcast or create_proof.

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 says 'Use after broadcast to see whether your proof has confirmed', anchoring the usage moment and naming the preceding sibling. It also notes the call is free, but gives no explicit when-not or polling-frequency guidance.

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.