Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_chart

Retrieve Google Finance price charts for a quote like AAPL:NASDAQ across windows from 1d to max, returning time, price, volume, current price, and change.

Instructions

Google Finance chart data. Returns the price chart for a Google Finance quote such as AAPL:NASDAQ or BTC-USD over a window from 1d to max (default 1d). Each point has a time, price and volume; the response also carries the instrument's name, exchange, currency, current price, change and previous close.

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote identifier such as AAPL:NASDAQ
windowNoWindow: 1d, 5d, 1m, 6m, ytd, 1y, 5y, max

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the per-point shape (time, price, volume) and the surrounding instrument metadata (name, exchange, currency, current price, change, previous close). It omits any mention of rate limits or auth, but the return behavior is well covered.

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 tightly written sentences with no filler, and the core purpose is front-loaded before the input/output detail. Nothing is wasted, though it is dense enough that a short scoping clause would have been welcome.

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?

No output schema exists, so the description must explain return values, and it does so adequately for a chart tool. The only meaningful gap is the absence of any routing against sibling quote/ticker tools.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real value beyond the schema: it supplies concrete quote-format examples and states the default window (`1d`), which the schema itself does not mention. The allowed window values are left to the schema, which is fine.

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+resource: returns the price chart for a Google Finance quote, with concrete identifier examples (`AAPL:NASDAQ`, `BTC-USD`). It clearly distinguishes chart/time-series data from a plain quote, but never names the obvious sibling (google_finance_quote) it should be contrasted with.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance. The description implies you call it to get a price chart, but given many sibling tools (google_finance_quote, google_finance_ticker, google_finance_search) the agent gets no help deciding between them.

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