List all crypto futures symbols currently tracked by TraderSpy with real-time candle data available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| symbols | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by specifying that symbols are 'currently tracked' and have 'real-time candle data available,' which indicates the data is live and relevant to candle-related tools. This adds value beyond the annotations.
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 a single, concise sentence that immediately conveys the tool's function. It is front-loaded with the verb and resource, and contains no unnecessary words or redundant information. Perfectly appropriate length.
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 tool's simplicity (no parameters, output schema exists), the description fully covers what the agent needs to know: that it lists tracked symbols with real-time candle data. The sibling tools are distinct, and the output schema handles return values. The description is sufficient for correct selection and invocation.
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 tool has zero parameters, so the description need not explain any. Per the rubric, with 0 params the baseline is 4. The description adds no parameter specifics, but none are needed since the schema is empty and schema description coverage is 100%.
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 purpose: 'List all crypto futures symbols currently tracked by TraderSpy with real-time candle data available.' It uses a specific verb (list) and resource (crypto futures symbols), and adds a distinguishing qualifier (tracked by TraderSpy, real-time candle data). This differentiates it from sibling tools like get_candles or get_price, which focus on specific symbols or data.
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 usage when you need an overview of tracked symbols, but it does not explicitly mention when to use this tool instead of alternatives like get_candles or get_market_stats. No exclusions or alternative recommendations are provided. The one-sentence description gives context but lacks explicit guidance.
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.
Most tools are clearly distinct, targeting different data categories (market data, signals, traders, account). Some potential overlap exists between get_price, get_candles, and get_market_stats, but their descriptions clarify the specific use cases. Overall, an agent can differentiate them reliably.
All tools follow a consistent verb_noun pattern with the verb 'get' and a descriptive noun (e.g., get_candles, get_signals, get_trader_profile). This uniform naming makes it very predictable for an agent.
With 15 tools, the count is within the ideal range for a domain-specific server. Each tool serves a distinct purpose related to market data, signals, and trader analytics, and none feel redundant or extraneous.
The tool set covers core read operations for market data, signals, traders, and account info, which aligns with the apparent purpose of a data-provider server. Minor gaps include lack of write operations (e.g., placing trades) or historical signal details beyond individual IDs, but these are not critical for a data-oriented service.