google_finance_context
Retrieve normalized financial context from Google Finance search results for any query.
Instructions
Returns normalized Google Finance context search results.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query |
Retrieve normalized financial context from Google Finance search results for any query.
Returns normalized Google Finance context search results.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must bear the full burden of behavioral disclosure. It merely states it 'returns normalized search results' without explaining what 'normalized' means, any side effects, rate limits, or prerequisites. This is insufficient for a tool with no 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 a single, concise sentence with no wasted words. However, it could be more informative while still being concise, hence a 4 rather than 5.
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 many sibling tools (notably google_finance_search), the description fails to clarify how 'context search results' differ from regular search. There is no output schema, and the description does not explain the scope or structure of the results. The tool could easily be confused with alternatives.
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 only parameter 'q' is described in the schema as 'Search query', and the description adds 'normalized Google Finance context' which adds little parameter-specific meaning. Since schema coverage is 100%, the baseline is 3, and no additional insight is provided.
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 returns 'normalized Google Finance context search results', which specifies the domain (Google Finance) and output type (search results, normalized). However, it does not distinguish from the sibling tool 'google_finance_search' which likely serves a similar purpose.
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 is provided on when to use this tool versus alternatives like google_finance_search or google_finance_quote. The description does not mention any prerequisites, exclusions, or context for appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server