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 the annotations. It mentions 'search for content' which aligns with read-only behavior but doesn't elaborate on search limitations, result formats, or any rate limits that might be relevant.

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 with a single sentence 'Search for content in QuantConnect.' It's front-loaded and wastes no words, though this brevity comes at the cost of completeness. Every word serves a purpose in stating the basic function.

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 1 parameter with 0% schema coverage, no output schema details provided in context, and annotations only covering read-only status, the description is inadequate. It doesn't explain what 'content' means, how results are returned, or provide any parameter guidance. For a search tool with complex nested parameters, this leaves too many gaps.

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 provides no information about the single parameter 'model' or its nested structure (SearchRequest with language and criteria). With no parameter details in the description to compensate for the schema gap, this leaves the agent guessing about required inputs.

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 'Search for content in QuantConnect' states a clear verb ('Search') and target ('content in QuantConnect'), but it's vague about what type of content and doesn't differentiate from siblings like 'read_file' or 'list_projects'. It provides basic purpose but lacks specificity about the search scope.

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 offers no guidance on when to use this tool versus alternatives. With siblings like 'read_file' for specific content access or 'list_projects' for listing resources, there's no indication of when search is appropriate versus direct retrieval methods. No usage context or exclusions are provided.

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