Fetch the current stock market quote for an individual ticker symbol. Returns real-time price, intraday change (dollars and percentage), trading volume, market capitalization, P/E ratio, earnings per share, dividend yield, and 52-week high/low. Use for real-time price monitoring, investment decisions, or financial dashboards.
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | Stock ticker symbol in uppercase (e.g. 'AAPL', 'MSFT', 'NVDA', 'TSLA') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description discloses real-time data and lists returned fields (e.g., intraday change, volume, PE). Consistent with annotations (readOnlyHint, openWorldHint). 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences covering purpose, output, and usage. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given simple tool with one parameter and no output schema, description sufficiently covers return content and use context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%; description adds example formats (uppercase) but doesn't provide meaning beyond schema. Baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb 'fetch' and resource 'stock market quote for an individual ticker symbol'. Clearly distinguishes from siblings 'compare_stocks' and 'get_multiple_quotes'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states use cases: 'real-time price monitoring, investment decisions, or financial dashboards'. Lacks when-not-to-use guidance relative to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: single quote, multiple quotes, and comparison. However, get_multiple_quotes and compare_stocks both handle multiple stocks, leading to slight overlap, but descriptions clarify different use cases.
All tools follow a consistent verb_noun snake_case pattern (get_stock_quote, get_multiple_quotes, compare_stocks), with no deviations.
Three tools is appropriate for a stock quote server covering single, multiple, and comparison queries; neither too few nor too many.
Core real-time quoting needs are covered (single, multiple, comparison). Minor gaps like historical data or symbol search exist but are not essential for the primary purpose.