Skip to main content
Glama

Theta transaction

theta_tx
Read-onlyIdempotent

Returns one Theta mainnet transaction by hash (the same data as web.oswave.io/tx/): type, block_height, timestamp, the full explorer record, and minted_card (v3:N) if it is a BrainVault mint. Read-only, free, no key; counts as 2 calls. Unknown hash: error not_found.

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

Input Schema

NameRequiredDescriptionDefault
hashYesTheta tx hash, 0x + 64 hex

Output Schema

NameRequiredDescriptionDefault
txNo
hashNo
typeNo
blockNo
staleNo
sourceNo
timestampNo
minted_cardNo
block_heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / hash / description
      Added value: +"Theta tx hash, 0x + 64 hex"
    • addedInput schema / properties / hash / pattern
      Added value: +"^0x[0-9a-fA-F]{64}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "block_height": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "hash": {
      +      "type": "string"
      +    },
      +    "minted_card": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    },
      +    "timestamp": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "tx": {
      +      "type": "object"
      +    },
      +    "type": {
      +      "type": [
      +        "integer",
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the description's job is to add operational context — and it does: free, no key required, credit cost of 2 calls, and explicit failure semantics ('Unknown hash: error not_found'). It also anchors expectations to the public explorer page for the same hash. Return-shape detail is not needed since an output schema exists.

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 core operation and return fields are front-loaded in the first clause, followed by the operational fragments (read-only, free, cost, error case). It is dense but every sentence carries information; the parenthetical 'full explorer record' is the only mildly vague element.

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 single-parameter lookup with an output schema and full annotation coverage, this is close to complete: it covers access, cost, and the one likely failure mode. The only gap is that 'counts as 2 calls' and 'the full explorer record' could be slightly more explicit about what an agent gets back, though the output schema handles that.

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 100% with a regex pattern documented on the schema itself, so baseline 3 applies. The description adds a small amount of meaning by tying the parameter to a human-verifiable web URL (web.oswave.io/tx/<hash>), which helps an agent source a valid hash.

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 ('Returns one Theta mainnet transaction by hash'), scopes it to mainnet, and enumerates the returned fields (type, block_height, timestamp, full explorer record, minted_card v3:N). The 'minted_card if it is a BrainVault mint' clause further distinguishes it from any generic lookup among the siblings.

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?

Usage is implied by the hash-based lookup framing, and it clarifies cost ('counts as 2 calls') and access ('free, no key'), which helps an agent decide whether to spend budget. However, it never names an alternative (e.g. theta_balance for balances) or states when not to use it, so routing guidance is left to inference.

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