Discover Tickbot’s ten active Coinbase USD forecast markets. Use search for a symbol or slug prefix.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | next_cursor returned by a prior get_instruments call. | |
| search | No | Case-insensitive COINBASE-SYMBOL-USD slug prefix or fragment, for example COINBASE-ADA-USD. | |
| exchange | No | ||
| asset_class | No |
Changes observed during successful MCP inspections.
Input schema / properties / exchange / enumPrevious value: -[
- "CRYPTO"
-]New value: +[
+ "COINBASE"
+]Input schema / properties / search / descriptionPrevious value: -"Case-insensitive CRYPTO-SYMBOL-USD slug prefix or fragment, for example CRYPTO-ADA-USD."New value: +"Case-insensitive COINBASE-SYMBOL-USD slug prefix or fragment, for example COINBASE-ADA-USD."Input schema / properties / asset_class / enumPrevious value: -[
- "CRYPTO",
- "US_STOCK"
-]New value: +[
+ "CRYPTO"
+]Input schema / properties / exchange / enumPrevious value: -[
- "BATS",
- "CRYPTO",
- "NASDAQ",
- "NYSE",
- "NYSEARCA"
-]New value: +[
+ "CRYPTO"
+]Input schema / properties / search / descriptionPrevious value: -"Case-insensitive instrument-slug prefix or fragment, for example CRYPTO-ADA or NASDAQ-AAPL."New value: +"Case-insensitive CRYPTO-SYMBOL-USD slug prefix or fragment, for example CRYPTO-ADA-USD."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only says 'Discover', implying a read operation, but does not mention pagination, rate limits, or side effects. It also fails to describe the return format, leaving the agent without critical behavioral context.
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 only two sentences, with the purpose front-loaded. It is concise and free of fluff, but the brevity sacrifices necessary detail about parameters and behavior.
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 tool has no output schema and no annotations, so the description must explain return values and usage. It only covers the purpose and search, omitting guidance on pagination, filtering, and what the response contains, making it incomplete for an agent to call correctly.
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 description adds minimal meaning to the search parameter, but the schema already describes it thoroughly. It does not explain limit, cursor, exchange, or asset_class, and with only 40% schema coverage, the description should compensate for these undocumented parameters, which it does not.
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 discovers Tickbot's ten active Coinbase USD forecast markets, using the specific verb 'Discover' and naming the resource. It does not explicitly differentiate from siblings, but the purpose is unambiguous.
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 advises using search for a symbol or slug prefix, which gives partial usage guidance. However, it does not explain when to use this tool versus alternatives like get_open_predictions, nor does it mention any exclusions or 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.