Retrieve normalized annual and quarterly financial statement rows for a quote identifier such as AAPL:NASDAQ when Google Finance provides data.
Google Finance financial statements. Returns normalized annual and quarterly financial rows when Google Finance has statement data for the quote.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 present, so description carries burden. It mentions conditional behavior ('when Google Finance has statement data') and output type, but lacks disclosure on mutation, rate limits, or authentication. Minimal transparency beyond core function.
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 front-loading purpose and output type with no superfluous 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 single parameter and no output schema, description covers output format and condition. Could be more complete by specifying which financial statements (income, balance sheet) are included, but adequate for basic usage.
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% and description adds no additional meaning beyond 'Quote identifier such as AAPL:NASDAQ' already in schema. Baseline score 3 applicable.
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 uses specific verb 'returns' and resource 'normalized annual and quarterly financial rows', clearly indicating it retrieves financial statements for a quote. It distinguishes from siblings like google_finance_quote which returns current quote data.
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 usage when financial statements are needed, but no explicit guidance on when to use this vs alternatives, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.