Skip to main content
Glama
Sign In

FreeTier Agent API

by dev.pages.freetier-agent-api
OverviewDiscussionsAdmin

Transaction status poller

tx_status
Read-only

3 free MCP calls per day (all tools together), then $0.0015 USDC via x402 or card credits (paid in-band: params._meta["x402/payment"]). Transaction status for polling: up to 10 tx hashes in one call, searched across Ethereum, Base, Arbitrum, Optimism and Polygon (or one chain): pending / success / failed / not_found, block, confirmations, finalized flag, from/to, gas used, fee in native coin, explorer link. When to use: Use tx-status to poll whether transactions are pending, confirmed, failed or finalized (up to 10 hashes, chain auto-detected). Use tx-explain for a full decode of one tx.

Input Schema

NameRequiredDescriptionDefault
hashYestx hash (0x + 64 hex), or comma list of up to 10
chainNoauto (default) searches all 5 chains

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties
      Removed value: -{
-  "at": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "count": {
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "heads": {
-    "properties": {
-      "arbitrum": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "base": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "ethereum": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "optimism": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "polygon": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "method": {
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "sources": {
-    "items": {
-      "properties": {
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "url": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "summary": {
-    "properties": {
-      "success": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "type": "object"
-  },
-  "txs": {
-    "items": {
-      "properties": {
-        "block": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "chain": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "chainId": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "confirmations": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "contract_created": {},
-        "effective_gas_price_gwei": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "explorer": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "fee_native": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "finalized": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "from": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "gas_used": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "hash": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "logs": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "native_coin": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "nonce": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "to": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value_native": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the quota (3 free calls/day across all tools), the paid fallback ($0.0015 USDC via x402 or card credits), and the in-band payment parameter location params._meta["x402/payment"]. That is meaningful operational context an agent cannot get from annotations. Slightly short of 5 because it does not say what happens when the quota is exhausted or payment is missing.

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 description is dense with no filler and the usage/alternative clause is clearly front-loaded after the scope statement. It loses a point because it re-enumerates the full return field list (block, confirmations, finalized flag, from/to, gas used, fee, explorer link) even though an output schema already exists, and it leads with pricing ahead of the core purpose.

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?

Given a two-parameter batch-read tool with full schema coverage, an output schema, and read-only annotations, the description supplies everything needed to call it correctly: batch limit, chain coverage and auto-detection, status semantics, cost model, and the sibling alternative. Nothing an agent needs 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%, so both parameters (hash, chain) are already fully documented including the 10-hash comma list and the enum for chain. The description mentions 'up to 10 tx hashes' and 'chain auto-detected,' but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Transaction status for polling') with concrete scope: up to 10 hashes, five named chains, and the exact status values returned. It explicitly names the sibling it is not ('Use tx-explain for a full decode of one tx'), so an agent can route 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 Guidelines5/5

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

Contains an explicit 'When to use' clause covering polling for pending/confirmed/failed/finalized transactions, plus the disambiguating alternative 'Use tx-explain for a full decode of one tx.' The selection condition between the two is stated outright rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FreeTier Agent API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources