Retrieve normalized classification strings for a stock quote such as AAPL:NASDAQ, converting raw ticker data into consistent category labels.
Google Finance classification data. Returns normalized classification strings for a 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 are provided, so the description carries the full burden. It states the tool returns normalized classification strings but lacks details on data freshness, API limits, authentication needs, or what 'normalized' means. Behavioral traits beyond the basic action are absent.
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 a single, front-loaded sentence that efficiently conveys the core function. However, it could be slightly expanded to include context without losing conciseness.
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 absence of an output schema and the large set of similar sibling tools, the description is incomplete. It does not hint at the output format or how this classification data differs from other google_finance endpoints like google_finance_quote.
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?
The input schema already describes the lone parameter ('quote') with a clear example. The description adds no additional meaning beyond the schema. Since schema coverage is 100%, baseline is 3.
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 that the tool returns normalized classification strings for a quote, using a specific verb ('Returns') and identifying the resource ('classification data'). It distinguishes itself from sibling google_finance tools by focusing on classification, but does not elaborate on what classification entails.
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 no guidance on when to use this tool versus other google_finance tools. There are many siblings (e.g., google_finance_quote, google_finance_ticker), but no comparison or exclusion criteria are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.