Server Details
MCP server for Yahoo Finance data including stock quotes, historical prices, company financials, and market news for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Tool Definition Quality
Average 3.1/5 across 3 of 3 tools scored.
Significant overlap exists between get_stock_quote and get_multiple_quotes, as both retrieve current quote data with no clear guidance on when to use the single-ticker variant versus the batch variant for individual requests. The distinction between compare_stocks and get_multiple_quotes is also vague regarding whether comparison analysis is server-side or merely formatted presentation.
All tools follow a consistent snake_case convention with verb-noun structure (compare_stocks, get_multiple_quotes, get_stock_quote). The pattern is predictable, though 'multiple_quotes' and 'stock_quote' exhibit minor inconsistency in granularity specification.
Three tools is insufficient for a comprehensive Yahoo Finance integration. The Yahoo Finance domain typically requires historical data, ticker search, financial statements, and news capabilities, making this set severely under-scoped for the server's stated purpose.
The surface covers only current quote retrieval with no support for historical price data, ticker symbol resolution/lookup, company fundamentals beyond basic quote metrics, or financial news. Agents cannot complete common workflows like trend analysis or discovering ticker symbols from company names.
Available Tools
3 toolscompare_stocksCRead-onlyInspect
Compare multiple stock securities side-by-side with key financial metrics and performance data. Returns price, P/E ratio, dividend yield, market cap, earnings, revenue, and relative performance for comparison. Use for investment analysis, selecting between stocks, or portfolio optimization.
| Name | Required | Description | Default |
|---|---|---|---|
| tickers | Yes | List of tickers to compare (minimum 2 for meaningful comparison) |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Mentions 'key metrics' but lacks specifics on what data is returned, rate limits, or computational cost despite no annotations.
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?
Extremely concise (9 words) and front-loaded, though brevity sacrifices necessary detail.
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?
Lacks output schema and fails to describe comparison format or specific metrics returned.
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?
With 0% schema coverage, description fails to explicitly document the 'tickers' parameter though 'multiple stocks' implies array input.
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?
States specific action (compare) and resource (stocks) with output type (key metrics), reasonably distinguishing from quote-fetching siblings.
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?
No guidance on when to use versus get_multiple_quotes or get_stock_quote alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_multiple_quotesBRead-onlyInspect
Fetch current stock quotes for multiple ticker symbols in one request. Returns price, change, volume, and key metrics for each stock. Use for portfolio monitoring, screening multiple stocks, or comparing multiple securities at once.
| Name | Required | Description | Default |
|---|---|---|---|
| tickers | Yes | List of stock ticker symbols to retrieve quotes for |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description fails to disclose data freshness, rate limits, or error handling 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely terse (8 words) and front-loaded, though slightly too lean given lack of schema descriptions.
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?
Adequate for simple tool structure but incomplete regarding parameter semantics and return value structure (no output schema).
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?
With 0% schema coverage, description must compensate but only hints at input with 'multiple stocks' without explaining array format or ticker symbol conventions.
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?
Clearly states it retrieves quotes for multiple stocks, distinguishing from sibling 'get_stock_quote' via 'multiple...at once'.
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?
Implies batch efficiency with 'at once' but lacks explicit when/when-not guidance versus single-quote tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_stock_quoteARead-onlyInspect
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') |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations or output schema exist, the description usefully discloses the specific data fields returned (price, change, volume, market cap, P/E ratio).
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?
Appropriately brief and front-loaded; two sentences efficiently cover action, input, and output without redundancy.
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?
For a simple single-parameter tool without output schema, the description is sufficient, covering functionality and return values adequately.
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?
With 0% schema description coverage, the description minimally compensates by referencing 'ticker symbol', but lacks format guidance (e.g., case sensitivity, exchange suffixes).
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?
Clear specific action ('Get') and resource ('current stock quote'), with return value details, though it doesn't explicitly distinguish single-ticker use from sibling '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?
No guidance on when to use this single-ticker tool versus the sibling 'get_multiple_quotes' for batch requests, or versus 'compare_stocks'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!