Crawlora MCP

google_finance_ticker

Read-only

Fetch Google Finance historical price and volume points when the instrument is supplied as separate first/second legs, such as AAPL + NASDAQ or BTC + USD with is_crypto=true. Returns window and series (time, price, volume); the default window is 1d and absent chart data returns not found. Prefer google_finance_chart for a combined quote identifier, instrument metadata, and available previous-close data; use google_finance_quote for a current overview.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "first": "<first>",
      "second": "<second>"
    },
    "name": "google_finance_ticker"
  }
}

Input Schema

Name	Required	Description
`first`	Yes	First leg of the ticker pair, for example AAPL or BTC.
`second`	Yes	Second leg, for example NASDAQ or USD.
`window`	No	Chart window: 1d (default), 5d, 1m, 6m, ytd, 1y, 5y, or max. ytd selects year-to-date; unsupported windows are rejected.
`is_crypto`	No	Whether the pair is a cryptocurrency pair.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / window / description

Previous value: -"Chart window such as 1d, 5d, 1m, 6m, 1y, 5y, or max (defaults to 1d)."New value: +"Chart window: 1d (default), 5d, 1m, 6m, ytd, 1y, 5y, or max. ytd selects year-to-date; unsupported windows are rejected."

First observedOct 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond them: it discloses the returned fields (window, series of time/price/volume), the default window of 1d, and the failure mode that absent chart data returns not found.

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 sentences, front-loaded with the action and its unusual parameter contract, then return behavior, then sibling routing. Dense but every sentence carries information; no filler.

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

Completeness5/5

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

With an output schema present, return-value documentation is not required, yet the description still summarizes the shape and the not-found case. Purpose, usage, alternatives, defaults, and error behavior together cover everything needed to invoke this tool correctly.

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 description coverage is 100%, so per-parameter meaning is already documented (baseline 3). The description adds value by showing how the params combine ('AAPL + NASDAQ or BTC + USD with is_crypto=true'), clarifying the first/second pairing semantics and the role of is_crypto beyond the individual field descriptions.

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?

States a specific verb (Fetch) and resource (Google Finance historical price and volume points) and pinpoints the unusual input shape it requires: separate first/second legs like AAPL + NASDAQ or BTC + USD. It explicitly differentiates itself from google_finance_chart and google_finance_quote, so an agent can route between them without opening schemas.

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

Usage Guidelines5/5

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

Gives the triggering condition (instrument supplied as separate first/second legs) and names two alternatives with the condition that selects each: google_finance_chart for a combined quote identifier, google_finance_quote for a current overview. Both when-to-use and when-to-prefer-something-else are present.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?