Skip to main content
Glama

Transaction Explainer

tx_status

Free: status (success, failed, pending), block, confirmations, fee, what kind of transaction it is, and how many red flags it has, without the details. About 20 calls a minute per client.

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": {
      "chain": "<chain>",
      "hash": "<hash>"
    },
    "name": "tx_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash, 0x followed by 64 hex characters
chainYesChain: ethereum, base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose real behavioral traits: it is free, it returns a summary rather than details, and it is rate limited to about 20 calls per minute per client. Missing only error/edge behavior (invalid hash, unsupported chain, pending-state caveats).

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?

A single dense sentence that front-loads the cost cue 'Free', then lists the returned fields and the rate limit. No filler or repetition.

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?

There is no output schema, so the description must convey the return shape, and it does enumerate the fields an agent gets back. Combined with the rate limit and summary-vs-detail scoping, this is nearly complete for a simple two-parameter read tool; only error handling is absent.

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 both parameters (hash format, chain values) are documented in the schema itself. The description adds no parameter-level meaning, so baseline 3 applies.

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 the resource (a transaction, identified by hash/chain) and enumerates the summary fields returned: status with the possible values success/failed/pending, block, confirmations, fee, type and red-flag count. That is concrete and distinguishable, though the verb is implied rather than stated and the sibling explain_transaction is only hinted at via 'without the details'.

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?

'Free' and 'without the details' imply this is the lightweight/cheap option versus a detailed lookup, which is usable guidance. But it never explicitly says when to choose it over the sibling or what happens for pending/unknown hashes, so usage is only implied.

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