Skip to main content
Glama
Sign In
quanttogo-mcp

quanttogo-mcp

by QuantToGo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

compare_strategies

Compare multiple strategies side-by-side by evaluating returns, drawdown, and recent performance to identify the best option.

Instructions

Compare multiple strategies side-by-side — returns, drawdown, and recent performance.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productIds": "<productIds>"
    },
    "name": "compare_strategies"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdsYesArray of product IDs to compare, e.g. ['PROD-E3X', 'PROD-PCR']

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It indicates a read-like operation but does not explicitly state it is safe, require authentication, or disclose side effects. The mention of returned metrics provides some insight, but behavioral traits beyond the obvious are missing.

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 sentence that is concise and densely informative, containing the verb, resource, and key comparison dimensions. No extraneous words or repetition.

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 low complexity (one parameter) and schema coverage, the description is adequate but lacks details about the output format or structure (e.g., table, percentages) which would help an agent interpret results. No differentiation from siblings or guidance on prerequisites.

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

Parameters3/5

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

Schema description coverage is 100% with a clear description for productIds. The tool description ('compare multiple strategies') adds no new semantic meaning beyond the schema, which already explains the parameter. Baseline score of 3 is appropriate.

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 verb 'Compare' and resource 'strategies', specifying the aspects compared: returns, drawdown, and recent performance. It implies side-by-side comparison, distinguishing it from single-strategy tools like get_strategy_performance, though not explicitly.

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

Usage Guidelines3/5

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

The description implies usage for comparing multiple strategies, but does not provide explicit guidance on when to use this tool versus siblings like list_strategies or get_strategy_performance. No exclusion criteria or alternative tools 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

Other Tools