Financial Data MCP Server

Get Stock Quote Tool

get_stock_quote_tool

Retrieve a stock's current quote by ticker to get live price, previous close, daily change, high/low, volume, and market state. Returns the data needed to assess a stock's latest trading activity.

Instructions

Get the current stock quote for a ticker symbol.

Returns live/latest price, previous close, day's change (absolute and percent), day high/low, volume, and market state (e.g. REGULAR, CLOSED, PRE).

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": {
      "ticker": "<ticker>"
    },
    "name": "get_stock_quote_tool"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Exact stock ticker symbol, e.g. "AAPL", "MSFT", "RELIANCE.NS". If you only have a company name, call search_ticker first.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are present, so the description carries the burden of explaining behavior. It clearly discloses the quote fields and market state examples, but it does not mention read-only side-effect absence, data freshness/delay, authentication needs, or behavior for invalid tickers.

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 two tightly written sentences with the core purpose front-loaded and the return payload summarized compactly. There is no redundancy or filler.

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 single-parameter quote tool with an output schema present, the description covers the core purpose and expected return data. The main gap is the lack of explicit behavioral caveats and alternative routing in the description itself, but nothing essential to invoking the tool 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%, so the baseline is 3. The tool description adds no parameter meaning beyond the word 'ticker symbol'; the schema already supplies exact-symbol guidance, examples, and the search_ticker fallback.

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 opens with a specific verb and resource: 'Get the current stock quote for a ticker symbol.' It then itemizes quote-specific fields such as live price, previous close, day high/low, volume, and market state, which clearly differentiates it from historical, overview, and ratio siblings.

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 when to use it through the word 'current' and the quote-specific return fields, so an agent can infer it is not for historical or fundamental analysis. However, it does not explicitly name alternative tools or state when-not-to-use conditions; the schema's search_ticker fallback is helpful but not part of the tool description.

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

Deploy Server