Get the exact USD price (cents) to claim a specific block at (x,y,w,h). Returns price_cents, tile_count, and zones spanned. v1.1 pricing: Center $300/tile, Corner $150/tile, Edge $75/tile.
| Name | Required | Description | Default |
|---|---|---|---|
| h | Yes | Height in tiles (1-20) | |
| w | Yes | Width in tiles (1-20) | |
| x | Yes | Top-left tile x (0-99) | |
| y | Yes | Top-left tile y (0-99) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool returns price_cents, tile_count, and zones spanned, and explains the pricing tiers (Center/Corner/Edge). However, it does not mention authentication needs, rate limits, or side effects. Basic transparency but missing non-obvious behavioral aspects.
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?
Two sentences plus a pricing line, all essential. The first sentence states purpose and return values, the second specifies pricing model. No filler, every sentence adds value. Well front-loaded.
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 the lack of output schema and annotations, the description provides basic return fields and pricing rules but lacks explanation of how zones are derived from coordinates and what the exact output format is. This may leave an agent uncertain about parsing results or interpreting zone context for different inputs.
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?
Schema has 100% coverage with clear descriptions (x,y in 0-99, w,h in 1-20). The description adds that parameters define a 'block' and mentions pricing zones, but does not explain how zones are determined from coordinates. Baseline 3 since schema already documents parameters well; description adds minimal extra meaning.
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 uses the specific verb 'Get' and clearly identifies the resource ('exact USD price (cents) to claim a specific block'). It distinguishes from siblings like 'claim_block' (action) and 'get_block' (info) by focusing on pricing before claiming.
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 implies use before claiming a block and provides pricing tier context. However, it does not explicitly state when not to use this tool or list alternatives (e.g., claim_quote_x402 might be for quotes). Guidance is implied but not explicit.
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.
Each tool serves a distinct purpose: block discovery, pricing, claiming, reading, survey operations, and service listing. No two tools are ambiguous in their function.
Most tools follow a verb_noun pattern (e.g., claim_block, get_block, list_services). The only outlier is 'price_check' which reverses the order, but it's still clear.
8 tools is well-scoped for the canvas domain, covering discovery, pricing, claiming, surveys, and service listing without overcomplicating the surface.
Core workflows (discover, price, claim, survey, list services) are covered. Missing a tool to register or update services, but the overall surface feels complete for the intended use.