Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_quote

Look up a stock or crypto symbol's Google Finance quote page to access key stats, company details, news, and income, balance sheet, and cash flow tables.

Instructions

Google Finance Quote API. Returns the Google Finance quote page for a symbol such as AAPL:NASDAQ or BTC-USD. The response carries key stats, an about section (CEO, employees, founded, headquarters, website), news, and investment tables for the income statement, balance sheet and cash flow by quarter and year.

Input Schema

NameRequiredDescriptionDefault
quoteYesStock symbol to fetch the latest quote for (e.g., AAPL:NASDAQ, BTC-USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden. It usefully enumerates the returned payload (key stats, about section, news, financial tables) in place of a missing output schema, but says nothing about access requirements, freshness, rate limits, or failure modes for an invalid symbol.

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?

Two dense sentences, front-loaded with the resource and then the payload contents. The opening 'Google Finance Quote API.' is mildly redundant with the tool name but the rest earns its place.

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 lookup with no output schema and no annotations, the description adequately covers both input format and the shape of the response. The only meaningful gap is routing guidance against the many overlapping google_finance_* siblings.

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 the single parameter is fully documented. The description's symbol examples (AAPL:NASDAQ, BTC-USD) duplicate what the schema already states, adding no new syntax or format detail, so the baseline 3 is correct.

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 Google Finance quote page for a symbol') and gives concrete symbol examples. It does not, however, distinguish itself from overlapping siblings like google_finance_ticker, google_finance_company, or google_finance_financials, whose content the description also claims to include.

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?

The description gives symbol-format examples but no when-to-use guidance, no exclusions, and no mention of alternatives such as google_finance_ticker or google_finance_financials. An agent must infer usage entirely.

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