Skip to main content
Glama
Sign In
MCP Yahoo Finance

MCP Yahoo Finance

by maxscheijen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_symbol_comparison

Compare current quote data for 1 to 20 stock symbols at once to evaluate side-by-side prices and changes.

Instructions

Compare current quote data for multiple stock 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": "get_symbol_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesOne to 20 Yahoo Finance symbols to compare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

B3.2/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 the full behavioral burden. 'Compare current quote data' implies a read-only operation, but it says nothing about return shape, whether the comparison is side-by-side, latency/rate-limit behavior, or how the 1-20 limit is enforced. For a zero-annotation tool this leaves real gaps.

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?

One sentence, front-loaded with the verb and scope, with no filler or redundancy. Appropriate size for a single-parameter read tool.

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

Completeness4/5

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

For a simple one-parameter read tool with full schema coverage and no output schema, the essentials are covered. A brief note on what the comparison returns or how it differs from the single-symbol tool would complete it, but nothing critical is missing.

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% and the single parameter already documents 'One to 20 Yahoo Finance symbols to compare,' including the format and bound. The description adds only the plural 'symbols' framing, so it does not meaningfully extend the schema.

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?

States a specific verb (compare) plus resource (current quote data) and scope (multiple symbols), which separates it from the single-symbol get_current_stock_price and get_rich_quote siblings. It does not name those siblings explicitly, so differentiation is inferable rather than stated.

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?

There is no when-to-use guidance and no mention of alternatives such as get_current_stock_price (single symbol) or get_rich_quote (deeper per-symbol data). An agent must infer the multi-symbol use case purely from the word 'multiple'.

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