Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_context

Search Google Finance by company name or ticker to get normalized instrument data including ticker, exchange, name, price, currency, and change.

Instructions

Find Google Finance instruments by query. Searches Google Finance for instruments matching a company name or ticker query and returns normalized results with ticker, exchange, name, price, currency, and change data. Use a returned ticker with quote, company, chart, or news endpoints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It discloses the return shape ('normalized results with ticker, exchange, name, price, currency, and change data'), which is useful. However, it does not mention whether the results are a list or single object, how many results may be returned, pagination behavior, or handling of ambiguous queries. For a search tool this is a moderate gap, keeping it at a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, all information-dense: purpose, return contents, and downstream usage. Front-loaded with the main verb and resource. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter search tool with no output schema and no annotations, the description covers the essential contract: what to query, what is returned, and how to use the result. It could additionally clarify result cardinality, but the listed fields and downstream endpoint guidance make it complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only says 'Search query' (100% coverage), but the description adds 'company name or ticker query', clarifying exactly what kind of string q accepts. This is meaningful added semantics beyond the schema field, so it earns a 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Find Google Finance instruments by query' – a specific verb and resource. It then specifies the search behavior and the exact returned fields, and distinguishes itself from detail endpoints by instructing the agent to use the returned ticker with quote, company, chart, or news endpoints. This makes the tool's role as a discovery/search step unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The final sentence gives clear downstream guidance: 'Use a returned ticker with quote, company, chart, or news endpoints.' This tells the agent when to stop using this tool and move to a detail endpoint. It does not explicitly name alternative search tools (e.g., google_finance_search) or state when not to use this tool, but the usage context is still well implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools