finstack-mcp

stock_quote

Get real-time stock quotes for global stocks including US, UK, European, Asian, and Indian markets. Returns price, change, volume, market cap, and more.

Instructions

Get real-time stock quote for any global stock.

Works for US, UK, European, Asian, and Indian stocks. Returns price, change, volume, market cap, P/E, sector, country, and more.

Args: symbol: Stock ticker symbol. Formats: - US stocks: AAPL, MSFT, GOOGL, TSLA, AMZN - UK stocks: HSBA.L, BP.L, VOD.L - Japan: 7203.T (Toyota), 6758.T (Sony) - Hong Kong: 0700.HK (Tencent) - India: RELIANCE.NS, TCS.NS (use nse_quote for Indian stocks)

Examples: stock_quote("AAPL") → Apple live price stock_quote("MSFT") → Microsoft live price stock_quote("TSLA") → Tesla live price

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": {
      "symbol": "<symbol>"
    },
    "name": "stock_quote"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Mar 26, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It states 'real-time' and lists returned fields, but doesn't mention data source, latency, error behavior for invalid symbols, or any limitations like delayed quotes for certain markets. This leaves the agent uncertain about edge cases.

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 well-structured with a clear opening, market coverage, returns list, and Args/Examples sections. It's slightly verbose due to repetition of region lists, but every sentence adds practical value, especially the symbol format examples.

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?

Given the tool's simplicity (one parameter) and the presence of an output schema, the description covers the essential knowledge: what it does, which symbols to use, and a relevant cross-reference to nse_quote. It lacks mention of limitations or when to prefer other real-time quote tools, which prevents a 5.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates by detailing symbol formats for US, UK, Japan, Hong Kong, and India, with concrete examples such as HSBA.L, 7203.T, and RELIANCE.NS. This goes far beyond the bare 'symbol' parameter in the schema and is essential for correct invocation.

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 starts with a specific verb+resource: 'Get real-time stock quote for any global stock.' It clearly distinguishes itself from siblings by emphasizing global coverage (US, UK, Europe, Asia, India) and explicitly points to nse_quote for Indian stocks, setting it apart from India-only quote tools.

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

Usage Guidelines4/5

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

It provides clear context: works for multiple regions and gives symbol format examples. It also directs users to nse_quote for Indian stocks, which is an explicit alternative. However, it doesn't compare against other similar quote tools like live_quote, fyers_live_quote, or icici_live_quote, so guidance for choosing between these is incomplete.

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

Deploy Server