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 retrieve matching instruments with ticker, exchange, price, currency, and change data, then feed ticker into quote, chart, or news endpoints.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
qYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the returned fields (ticker, exchange, name, price, currency, change), which is valuable given there is no output schema. It does not, however, state whether it is read-only, whether auth or rate limits apply, or result-count/pagination behavior.

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

Conciseness4/5

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

Three tight sentences with the core purpose front-loaded, followed by output fields and a usage note. No filler, though it could be compressed slightly.

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 simple one-parameter lookup with no annotations or output schema, the description covers purpose, expected output fields, and the intended next step. It is largely complete, with the only gap being lack of guidance against sibling alternatives.

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

Parameters3/5

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

Schema description coverage is 100% and there is a single parameter, so the baseline is 3. The description adds only marginal meaning by indicating the query matches a company name or ticker, which slightly enriches the bare 'Search query' schema text but no syntax or format details.

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

Purpose4/5

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

States a specific verb (Find/Searches) and resource (Google Finance instruments) and clarifies the input domain (company name or ticker query). It is distinguishable from retrieval siblings like google_finance_quote by describing itself as a search step, though it never explicitly names the sibling google_finance_search or google_finance_ticker that could be confused with it.

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

Usage Guidelines3/5

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

The final sentence gives downstream usage guidance ('Use a returned ticker with quote, company, chart, or news endpoints'), which is helpful context. However, it never states when to prefer this tool over the many other google_finance lookup/search siblings, so selection guidance is only 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