Look up several OpenSea collections at once with listed-item counts by marketplace. Use opensea_collection for one collection or opensea_search_collections to find collections.
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes | Comma-separated OpenSea collection slugs, at most 50. Required. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful note that results include listed-item counts broken down by marketplace, but it says nothing about rate limits, slug resolution failures, or batching behavior. With annotations carrying the safety burden, a 3 is appropriate.
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 tight sentences, zero waste. The capability is front-loaded and the routing guidance follows immediately, which is the correct ordering for an agent scanning for tool fit.
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?
With an output schema present, return values need not be explained, and annotations plus the single fully-documented parameter leave little else to cover. The description states scope and alternatives adequately; only minor behavioral detail (e.g., how missing slugs are handled) is absent.
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 description coverage is 100% and the single 'slugs' parameter is fully documented in the schema, including the comma-separated format and the 50-slug cap. The description only implies multiplicity ('several ... at once'), adding no syntax detail beyond the schema. Baseline 3 when the schema does the heavy lifting.
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?
States a specific verb ('Look up'), resource ('OpenSea collections'), and batch scope ('several ... at once') plus what the result contains ('listed-item counts by marketplace'). This clearly distinguishes it from the singular opensea_collection and the discovery-oriented opensea_search_collections.
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?
Explicitly names both alternatives and the condition selecting each: 'Use opensea_collection for one collection or opensea_search_collections to find collections.' The agent knows exactly when to prefer this batch tool over its siblings.
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.
