Yahoo Finance MCP Server
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
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 3 of 3 tools scored.
The tools have distinct purposes: single quote, multiple quotes, and comparison. There is minor overlap in returned metrics between get_multiple_quotes and compare_stocks, but the use cases are clearly different (monitoring vs. comparison).
All tool names follow a consistent verb_noun pattern in snake_case: get_stock_quote, get_multiple_quotes, compare_stocks. The convention is uniform and predictable.
With 3 tools, the server is well-scoped for basic stock data retrieval and comparison. No unnecessary tools and no obvious need for more given its domain.
The tool surface covers single quotes, bulk quotes, and side-by-side comparison. Minor gaps like historical data or ticker search exist, but the core functionality for real-time stock analysis is well-covered.
Available Tools
3 toolscompare_stocksARead-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?
Annotations already indicate read-only behavior; description adds value by listing exact metrics returned (price, P/E, yield, etc.) and confirming no side effects.
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 sentences, extremely concise, with no redundancy. Each sentence earns its place: first defines action and outputs, second states use cases.
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?
Despite no output schema, description lists all key returned metrics, sufficient for understanding. Covers the single-parameter complexity well.
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% with param description. The description adds the extra constraint that a minimum of 2 tickers is needed for meaningful comparison, which aids usage.
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?
The description clearly states the tool compares multiple stock securities with specific financial metrics and performance data, distinguishing it from similar tools like get_multiple_quotes and get_stock_quote.
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?
Provides clear use cases (investment analysis, stock selection, portfolio optimization) but does not explicitly mention when not to use the tool or compare to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_multiple_quotesARead-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?
Annotations already indicate readOnlyHint=true and openWorldHint=true, so the description adds value by specifying returned data (price, change, volume, key metrics). No additional behavioral warnings are needed, but it could mention potential variability due to openWorldHint.
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?
The description is concise with three sentences, no redundancy, and front-loaded with the primary action. Every sentence adds value.
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 no output schema, the description explains return fields partially. It covers core metrics but could specify additional details like structure or error handling. Still sufficient for basic use.
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 description coverage is 100% with a clear description for 'tickers'. The tool description adds no new parameter semantics beyond restating 'multiple ticker symbols', which is already covered. Baseline 3 is appropriate.
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?
The description clearly states it fetches current stock quotes for multiple ticker symbols, differentiating from sibling tools like get_stock_quote (single) and compare_stocks (comparison) by specifying 'multiple' and 'in one request'.
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?
The description gives clear use cases: portfolio monitoring, screening, comparing multiple securities. However, it does not explicitly state when not to use or alternative tools, but the context is sufficient for an AI agent.
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?
The description adds meaningful behavioral context beyond annotations by detailing the specific data returned (e.g., intraday change, market cap, P/E ratio). It does not contradict the readOnlyHint or openWorldHint 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?
The description is concise with two sentences: the first states the core action, and the second lists returned fields and use cases. No extraneous information.
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 the simplicity of the tool (one required parameter, read-only, open world), the description sufficiently covers the return values and usage context, making it complete for an agent to understand its behavior.
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?
Since schema coverage is 100% and the description mentions 'ticker symbol' without adding new details beyond the schema's description, the parameter semantics are adequately covered but not enhanced.
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?
The description clearly states it fetches a stock quote for an individual ticker symbol, using a specific verb and resource. It distinguishes itself from siblings by emphasizing 'individual ticker symbol' as opposed to comparing or fetching 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?
The description provides clear usage context like real-time price monitoring and investment decisions, but does not explicitly state when not to use this tool or compare it against siblings, lacking exclusionary guidance.
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
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
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!