Compute the Merkle root for a set of CryptoPunk IDs. The root matches the on-chain Solady MerkleProofLib encoding used by the Stash contract. Rate limit: 5 per 10 min (compute bucket — shared with filter_punks, resolve_merkle_root).
| Name | Required | Description | Default |
|---|---|---|---|
| punkIds | Yes | Punk IDs to include in the Merkle tree (1-10000) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already indicates a safe read-only operation. The description adds valuable context about the on-chain Solady MerkleProofLib encoding and a detailed rate limit shared with siblings, going beyond the annotation. No contradiction exists.
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?
Three tight, information-dense sentences: the core action, the encoding context, and the rate-limit constraint. No verbose phrasing or redundant details.
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?
The description covers purpose, encoding standard, and operational limits, but omits any mention of the return value format or error behavior. Since there is no output schema, this is a gap, though the simple tool and the name partially compensate.
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 input schema provides a complete description of the punkIds parameter (100% coverage), so the description does not need to add much. It only repeats that IDs are included without adding any new parameter meaning, warranting the baseline score.
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 computes a Merkle root from a set of CryptoPunk IDs, using a specific verb and resource. However, it does not differentiate from the sibling tool resolve_merkle_root, so it lacks explicit sibling distinction.
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?
No explicit when-to-use or alternative guidance is provided. The purpose implies usage when a Merkle root is needed, but there is no mention of how this relates to resolve_merkle_root or when one should be preferred over the other, despite sharing a rate-limit bucket.
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.
Every tool targets a distinct resource or action: trait/type browsing, punk metadata, listings/floor price, bids by root/punk, Merkle computation/filtering/resolution, and bid recommendations. The related Merkle tools have clear boundaries: compute builds a root from IDs, filter returns IDs for a trait selection, and resolve reverses a root only if it has bids.
All tool names follow a consistent `verb_noun` pattern in snake_case (e.g., browse_traits, get_floor_price, resolve_merkle_root). The two bid lookup tools use the same `get_bids_for_X` structure, reinforcing predictability.
Eleven tools is well within the ideal 3-15 range and each covers a necessary facet of the CryptoPunks domain—from market data (listings, floor) to trait-based bid analysis (merkle roots, recommendations). No redundancy or bloat.
The tool surface covers the full read-side lifecycle: viewing traits/types/punks, checking market prices/listings, analyzing existing bids, and supporting trait-based bid strategies through Merkle root operations and recommendations. It lacks write actions (e.g., placing bids), but the server's purpose is clearly analytical, so no obvious operational gap exists.