Skip to main content
Glama
Sign In
trading-mcp-server

trading-mcp-server

by mukul8896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

compare_multiple_symbols

Compare indicator snapshots side-by-side for up to 10 symbols. Select a timeframe to analyze market data and indicators across multiple assets.

Instructions

Side-by-side indicator snapshots for up to 10 symbols.

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": {
      "symbols": "<symbols>"
    },
    "name": "compare_multiple_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes
timeframeNoONE_DAY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only says 'indicator snapshots' without detailing what data is returned, whether it is read-only, or any behavioral traits like rate limits or pagination. The bound of 'up to 10 symbols' is the only behavioral hint.

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 a single, front-loaded sentence with zero wasted words. It is efficient but very brief, sacrificing detail for brevity.

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 lack of annotations, output schema, and sibling differentiation, the description is incomplete. It does not convey the expected output format, how the 'side-by-side' display works, or how this tool relates to similar sibling tools like get_indicator_snapshot.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the purpose or format of the two parameters ('symbols' and 'timeframe'). No allowed values, defaults, or examples are mentioned, leaving the agent to infer from parameter names alone.

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 tool does 'side-by-side indicator snapshots' for up to 10 symbols. This specifies a unique verb-resource combination (compare snapshots) and distinguishes it from single-symbol tools like get_indicator_snapshot.

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 indicators across multiple symbols but does not explicitly state when to use this tool versus alternatives (e.g., get_indicator_snapshot or fetch_historical_data). No when-not or exclusion conditions are provided.

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