Skip to main content
Glama
taylorwilsdon

QuantConnect MCP Server

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

clear_quantconnect_auth

Remove authentication credentials for the QuantConnect trading platform to reset access or switch accounts.

Instructions

Clear current QuantConnect authentication configuration.

Returns: Dictionary containing operation status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • quantconnect_mcp/src/tools/auth_tools.py:187-213 (handler)
    Handler function for the 'clear_quantconnect_auth' MCP tool. Decorated with @mcp.tool() inside register_auth_tools, clears the authentication instance by setting quantconnect_auth._auth_instance to None.
    @mcp.tool()
async def clear_quantconnect_auth() -> Dict[str, Any]:
    """
    Clear current QuantConnect authentication configuration.

    Returns:
        Dictionary containing operation status
    """
    try:
        from ..auth import quantconnect_auth  # type: ignore

        # Clear the auth instance
        quantconnect_auth._auth_instance = None

        return {
            "status": "success",
            "message": "QuantConnect authentication cleared successfully",
            "authenticated": False,
        }

    except Exception as e:
        return {
            "status": "error",
            "error": str(e),
            "message": "Failed to clear authentication",
        }
  • quantconnect_mcp/main.py:46-52 (registration)
    Registration of auth tools module in the main entry point by calling register_auth_tools(mcp), which defines and registers the clear_quantconnect_auth tool.
    safe_print("🔧 Registering QuantConnect tools...")
register_auth_tools(mcp)
register_project_tools(mcp)
register_file_tools(mcp)
register_backtest_tools(mcp)
register_live_tools(mcp)
register_optimization_tools(mcp)

Tool Definition Quality

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool clears auth configuration and returns a status dictionary, which covers basic behavior. However, it lacks details on side effects (e.g., whether this invalidates active sessions), permissions required, or error conditions, leaving gaps for a mutation tool.

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

Conciseness4/5

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

The description is concise and front-loaded, with the core purpose stated first and return information added efficiently. Both sentences earn their place, though it could be slightly more structured (e.g., separating behavior from returns).

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

Completeness3/5

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

Given the tool's complexity (a mutation with no annotations but an output schema), the description is moderately complete. It explains what the tool does and the return format, but lacks context on when to use it, side effects, or error handling, which would be helpful for safe invocation.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description appropriately avoids redundant information about inputs.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Clear') and resource ('QuantConnect authentication configuration'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from its sibling 'configure_quantconnect_auth' or 'validate_quantconnect_auth', which would have earned a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'configure_quantconnect_auth' or 'validate_quantconnect_auth'. It doesn't mention prerequisites (e.g., needing existing auth to clear) or consequences, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/quantconnect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server