Calculate key technical indicators like RSI, SMAs, VWAP, and Bollinger Bands for a symbol over a chosen timeframe to evaluate market conditions and support trading decisions.
Calculate technical indicators (RSI, SMAs, VWAP, Bollinger Bands) for a given symbol over a timeframe.
| Name | Required | Description | Default |
|---|---|---|---|
| endTime | Yes | ||
| interval | No | ||
| symbolId | Yes | ||
| startTime | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the action but does not disclose whether this is read-only, requires permissions, has rate limits, or what happens with insufficient data. It adds no traits beyond the stated calculation.
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 with no filler. It front-loads the verb and resource, making the purpose immediately clear.
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?
For a four-parameter tool with no output schema and no annotations, this description is too sparse. It does not describe the return shape, interval options, or time format requirements, so an agent may call it with incorrect or incomplete 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 description coverage is 0%, so the description must compensate. It maps 'symbol' and 'timeframe' to symbolId and startTime/endTime, but it does not explain the 'interval' parameter or time string formats. Several parameters remain undocumented by both schema and description.
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 a specific verb ('Calculate') and names the resource ('technical indicators') with explicit indicator list (RSI, SMAs, VWAP, Bollinger Bands). It clearly distinguishes this from sibling tools like qt_get_candles, which fetch raw price data, and qt_compare_symbols, which compare symbols.
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 gives no guidance on when to use this tool versus alternatives. It does not mention qt_get_candles for raw data or any exclusions, so an agent must infer the use case from the name and description alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.