TON/Gram latest masterchain block: seqno, workchain, shard tip. The chain tip for The Open Network (Telegram's chain, tvm:-239). Send {}. [x402 paid tool — price $0.001; POST /api/ton/block]
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as rate limits, destructive potential, or authentication requirements. The fact that it's a paid tool is mentioned, but safety or idempotency is not addressed.
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 concise and front-loaded with the key purpose. It includes essential supplementary info (payment, endpoint) without excess. Could be slightly more structured but is effective.
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?
Given no output schema, the description lists some return fields but may omit others. It provides enough context for a simple block tip tool, but lacks details like chain confirmation status or additional metadata.
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?
There are no parameters, so the description adds value by explaining the output fields (seqno, workchain, shard tip). The baseline for no parameters is 4, and the description meets that.
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 'TON/Gram latest masterchain block' and specifies the returned fields (seqno, workchain, shard tip), making the tool's purpose specific and distinct from sibling tools.
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 mentions it's a paid tool and includes the HTTP endpoint, implying usage context, but does not explicitly guide when to use this tool versus alternatives or state any prerequisites.
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.
Tools are organized by domain prefix (e.g., 'crypto_', 'rh_', 'snipe_'), which helps distinguish between areas. Within each domain, they serve distinct purposes, though some overlap between domains exists (e.g., price data appears in multiple groups). Overall, an agent can navigate effectively.
All tool names follow a consistent snake_case pattern with a domain prefix and a verb_noun combination (e.g., 'compliance_risk', 'rh_stock', 'snipe_honeypot'). This makes the API predictable and easy to explore.
With 159 tools, the server is extremely large. While the broad scope of web3 and utility functions justifies many tools, the count is significantly above the typical range for a coherent toolkit, potentially overwhelming agents and increasing selection error.
The toolkit covers a wide range of web3 operations: crypto, DeFi, compliance, safety, scheduling, memory, etc. There are no obvious major gaps for its intended purpose, though some niche areas might be missing.