Retrieve normalized news articles for a specified Google Finance quote, with an optional limit, to support finance research and quote monitoring.
Google Finance quote news. Returns normalized news articles for a quote.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Article limit | |
| quote | Yes | Quote identifier such as AAPL:NASDAQ |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so description must carry the burden. It only says 'returns normalized news' but omits behavioral details like freshness, ordering, pagination, or what 'normalized' means. Lacks disclosure of side effects or limits (e.g., default limit).
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 with no redundancy. Front-loads purpose and result. Every word is necessary.
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, more detail on the return format would help. Also, with numerous sibling tools, missing context on how this differs from other Google Finance news tools or generic news tools reduces completeness for a complex domain.
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%, so baseline is 3. Description adds no extra meaning beyond schema; 'for a quote' matches the 'quote' param. No new semantics for 'limit' either.
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 verb and resource: 'returns normalized news articles for a quote'. However, it doesn't distinguish among siblings like google_finance_analyst_articles (analyst news) or google_finance_markets_category_news (category news).
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 vs other news tools or alternatives. Usage is implied but not explicit, and no exclusions or conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.