Verify a Base mainnet tx hash actually moved USDC: decodes every USDC Transfer log in the receipt (from, to, amount) and answers settled true/false — the check an x402 seller runs before trusting a payment reference. $0.004/call via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| tx | Yes | Transaction hash to verify, 0x-prefixed 64 hex chars |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the internal behavior: 'decodes every USDC Transfer log in the receipt (from, to, amount)' and the binary outcome 'settled true/false'. It also transparently states the cost ($0.004/call). Missing edge cases like what happens for non-USDC or non-existent transactions, but the provided detail is above average.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single well-structured sentence that front-loads the core purpose ('Verify a Base mainnet tx hash'), then elaborates with mechanism, use case, and cost. Every phrase earns its place; no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description is complete: it explains what the tool checks, how it checks it, what it returns (true/false), when to use it, and the cost. The sibling context shows it's well-positioned among related tools, and the description fully satisfies the need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already fully describes the single 'tx' parameter with pattern and description, giving 100% coverage. The description adds valuable semantic context by specifying this is a 'Base mainnet tx hash' and that it's specifically for USDC, which is not in the schema. This elevates it above the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's specific verb and resource: 'Verify a Base mainnet tx hash actually moved USDC'. It goes further by explaining it decodes every USDC Transfer log and answers settled true/false, which sharply distinguishes it from sibling tools like base_tx_status or base_usdc_balance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context: 'the check an x402 seller runs before trusting a payment reference'. This tells the agent exactly when to use it. However, it doesn't explicitly mention alternatives or when not to use it, such as when a simpler tx status check would suffice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tool groups are nearly indistinguishable: wallet_analyze, wallet_spy, and base_wallet_profile all inspect wallets; batch_extract, batch_url_json, and x401_batch_extract all batch-extract URLs; route_task, agentcore_route, and mpp_route all perform routing. An agent would need to read very carefully to avoid selecting the wrong tool.
All names are snake_case, but there is no consistent verb_noun or namespace pattern: many are noun-only (inference, echo, sentiment, server_time), some are prefixed by domain (bazaar_, base_, x402_, rep_), and action prefixes vary widely (fetch_, compile_, extract_, purchase_, route_). The naming is readable but not predictable across the set.
Seventy tools is an extremely large surface for an agent to choose from, and most appear to be independent paid service wrappers. This exceeds the 50+ extreme mismatch threshold in the calibration and creates an overwhelming selection problem.
Relative to its apparent purpose—exposing x402 payments and Bazaar market data—the coverage is extensive: diagnostics, preflight, settlement verification, receipt lookup, wallet checks, Bazaar analytics, web extraction, and text processing are all represented. The main gaps are operational side-effects like creating or updating a Bazaar listing, but those appear to be outside this read/purchase surface.