FinanceKit MCP

stock_quote

Read-only

Get real-time stock price, change, volume, and key metrics like P/E ratio and market cap for any ticker symbol.

Instructions

Get the current stock price, change, volume, and key metrics for a ticker.

Returns real-time market data including price, daily change, 52-week range, P/E ratio, market cap, and more.

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	Stock ticker symbol (e.g., AAPL, MSFT, TSLA)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0May 1, 2026
Removedv1.2.0May 1, 2026
First observedv0.1.0Apr 16, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The readOnlyHint annotation already indicates a safe read operation. The description adds valuable context about the returned data (real-time price, daily change, 52-week range, P/E ratio, market cap, etc.), which goes beyond the annotation. No contradictions.

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 sentences. The first sentence immediately states the core purpose, and the second adds more specific details. No unnecessary words or repetition.

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 single-parameter tool that retrieves real-time data, the description is complete. It mentions the key metrics returned, and the presence of an output schema (not shown) likely documents the return format. No additional context seems necessary.

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?

There is a single parameter 'symbol' with a schema description that includes examples (AAPL, MSFT, TSLA). The description mentions 'ticker' which is essentially synonymous. Since schema coverage is 100% and the description adds minimal new info beyond the schema, baseline 3 is appropriate.

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 returns current stock price, change, volume, and key metrics for a ticker, using a specific verb 'Get' and resource 'current stock price... for a ticker'. It distinguishes itself from siblings like 'price_history' (historical data) and 'multi_quote' (multiple tickers).

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?

The description does not provide any guidance on when to use this tool versus alternatives like 'company_info', 'price_history', or 'multi_quote'. There is no explicit statement of when not to use it or which sibling handles related but distinct queries.

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

Deploy Server