QuantConnect MCP Server

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

Annotations include 'readOnlyHint: true', indicating this is a safe read operation. The description doesn't contradict this, as 'Show' aligns with reading. However, it adds minimal behavioral context beyond annotations—no details on rate limits, authentication needs, or what 'show' entails (e.g., real-time suggestions, batch processing). With annotations covering safety, the description provides some value but lacks depth.

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, clear sentence with no wasted words, making it easy to parse. It's front-loaded with the core action. However, it could be more structured by including key details, but as-is, it's efficiently concise without being overly brief.

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 annotations (readOnlyHint) and an output schema, the description doesn't need to explain safety or return values. However, with 0% schema coverage and no behavioral details, it's incomplete for a tool that likely involves AI or complex processing. It meets a minimal standard but leaves gaps in understanding how to use it effectively.

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%, meaning parameters are undocumented in the schema. The description mentions 'a specific text input', which hints at the 'sentence' parameter but doesn't explain the 'model' object, 'language', or 'responseSizeLimit'. It adds marginal meaning but doesn't fully compensate for the schema gap, leaving key parameters unclear.

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 'Show the code completion for a specific text input' clearly states the tool's purpose (verb: 'Show', resource: 'code completion') but is somewhat vague. It doesn't specify what kind of code completion (e.g., AI-based, IDE-like) or how it differs from sibling tools like 'check_syntax' or 'update_code_to_pep8', leaving room for ambiguity about its exact function.

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, context (e.g., for programming assistance), or exclusions, and doesn't reference sibling tools. This lack of usage context makes it harder for an agent to decide when this tool is appropriate.

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