QuantConnect MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds no behavioral context beyond what annotations provide - no information about pagination behavior (implied by start/end parameters), rate limits, authentication requirements, or what format the insights are returned in. With annotations covering the safety profile, this meets the minimum baseline.

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 extremely concise - a single sentence with no wasted words. However, this conciseness comes at the cost of being under-specified. While structurally simple, it lacks the necessary detail for a tool with complex parameter requirements.

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 that this tool has an output schema (which handles return values) and annotations covering read-only safety, the description should focus on usage context and parameter guidance. However, it fails to explain the paginated nature of insights retrieval, the relationship between parameters, or when to use this versus other backtest reading tools. For a tool with 4 nested parameters and sibling alternatives, this is insufficient.

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% (the single parameter 'model' has no description in the schema), and the tool description provides absolutely no information about parameters. The description doesn't mention that insights are fetched using a range (start/end), require project and backtest IDs, or have a 100-item limit. This leaves all parameter semantics undocumented.

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 'Read out the insights of a backtest' clearly states the verb ('read out') and resource ('insights of a backtest'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'read_backtest' or 'read_live_insights', leaving ambiguity about what specifically distinguishes this tool from other read operations in the system.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for reading different aspects of backtests (e.g., 'read_backtest', 'read_backtest_chart', 'read_backtest_orders'), but the description doesn't explain when this specific insights-reading tool is appropriate versus those other options.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.