QuantConnect MCP Server

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description doesn't contradict this but adds minimal behavioral context beyond annotations—it doesn't disclose rate limits, authentication needs, or what data is returned. Since annotations cover the safety profile, the bar is lower, but the description could still add more operational 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 extremely concise—a single three-word sentence—with zero wasted words. It's front-loaded and efficiently states the core action, though this brevity comes at the cost of completeness. No structural issues are present.

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 has one parameter with 0% schema coverage, an output schema exists (which helps), but the description is inadequate. It doesn't explain what an 'optimization' is in this context, how to use the tool, or what to expect in return. For a read operation with a required ID parameter, more context is needed to guide effective use.

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 schema provides no parameter descriptions. The tool description doesn't mention parameters at all, failing to compensate for the schema gap. It doesn't explain what 'optimizationId' represents, its format, or where to obtain it, leaving the agent with minimal guidance.

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 an optimization' is a tautology that restates the tool name without adding meaningful context. It doesn't specify what 'optimization' refers to in this domain or what aspects are being read. While it includes a verb ('Read') and resource ('optimization'), it lacks the specificity needed to distinguish it from sibling tools like 'list_optimizations' or 'update_optimization'.

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. It doesn't mention prerequisites (e.g., needing an optimization ID), differentiate from 'list_optimizations' (which likely lists multiple optimizations), or specify use cases. The agent must infer usage solely from the tool name and schema.

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