Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_ticker

Fetch Google Finance price series for a ticker like AAPL:NASDAQ or BTC-USD, with time, price, and volume points plus selectable windows from 1d to max.

Instructions

Google Finance Ticker API. Returns the price series Google Finance charts for a ticker such as AAPL:NASDAQ or BTC-USD. window sets the range: 1d (default), 5d, 1m, 6m, ytd, 1y, 5y or max. Each point has a time, price and volume.

Input Schema

NameRequiredDescriptionDefault
tickerYesTicker symbol to fetch data for example:AAPL:NASDAQ, BTC-USD
windowNoTime window for the ticker data (default: 1d), options: 1d, 5d, 1m, 6m, 1y, 5y, max

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape (time/price/volume) and the default window, but is silent on auth needs, rate limits, or error behavior for invalid tickers.

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 tight sentences, front-loaded with what the tool returns, followed by the range parameter and the point structure. No filler.

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?

With no output schema and no annotations, the description compensates well by naming the returned fields (time, price, volume) and the default/optional window. A richer note on ticker validity or data granularity would make it complete.

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% (baseline 3), and the description goes beyond the schema by adding the `ytd` window value not listed in the schema's option set, and by restating the default and the ticker format. This is modest but genuine added meaning.

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 and resource ('Returns the price series Google Finance charts for a ticker') with concrete ticker examples. It is clear what the tool does, though it does not explicitly differentiate itself from near-siblings like google_finance_chart or google_finance_quote.

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?

Usage is implied: use this to get a price series for a ticker, and `window` controls the range. There is no explicit when-to-use guidance nor any named alternative among the many google_finance siblings, so the agent must infer the boundary itself.

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