Search Google Finance by keyword to fetch normalized results for stocks, companies, and financial data. Returns clean JSON for market research queries.
Google Finance Search API. Fetches normalized search results for a provided keyword from Google Finance.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Keyword to search for (e.g., Apple) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses it fetches results, but does not specify read-only nature, auth needs, rate limits, or side effects. Adequate but minimal.
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 at two sentences, no unnecessary words. The first sentence names the API, the second describes the action efficiently.
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 one-parameter tool with no output schema, the description is mostly complete. It explains the action and parameter, but lacks details on the format of search results (e.g., tickers, companies). Minor gap.
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% for the single parameter 'q', and the description mentions 'provided keyword' with an example, adding no extra meaning beyond the schema. Baseline score applies.
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 normalized search results from Google Finance for a keyword, using a specific verb and resource. It distinguishes from sibling tools like google_finance_quote or yahoo_finance_search by focusing on keyword search.
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 explicit guidance on when to use this tool versus alternatives like google_finance_company or google_finance_quote. The description does not provide context for selection among many finance-related siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.