QuantConnect MCP Server

read_object_store_file_download_url

Read-only

Generate a secure download URL to access files stored in QuantConnect's Object Store for algorithmic trading data retrieval.

Instructions

Get the URL for downloading files from the Object Store.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`model`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	The URL to download the object. This can also be null. To download the object, paste the full URL (including the URL parameters) into a browser.
`jobId`	No	Id of the job, which you can use to request a download URL.
`errors`	No	List of errors with the API call.
`success`	No	Indicate if the API request was successful.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Feb 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description is consistent. However, no additional behavioral context (e.g., URL expiration, auth requirements) is added, so it meets the baseline without adding value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words, perfectly concise for its purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has a nested parameter with two required fields and an output schema, the description lacks details about input requirements and relationships to sibling tools like read_object_store_file_job_id, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the description does not mention any parameters. The schema itself describes organizationId and jobId, but the description adds no meaning to help the agent understand what to provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'URL for downloading files from the Object Store', distinguishing it from sibling tools like read_object_store_file_job_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool, prerequisites (e.g., need a job ID), or alternatives are provided. Sibling tools exist but no exclusions are mentioned.

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

Deploy Server