Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_quote

Fetch current stock or crypto quote data from Google Finance by providing a ticker symbol like AAPL:NASDAQ or BTC-USD. Returns clean JSON for finance tracking and analysis.

Instructions

Google Finance Quote API. Fetches the latest quote data for a provided stock symbol from Google Finance https://www.google.com/finance/quote/AAPL:NASDAQ?hl=en.

Input Schema

TableJSON 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
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the basic action without revealing any side effects, rate limits, or prerequisites. No mention of what 'quote data' includes or excludes.

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 short sentences are efficient. However, the second sentence is a URL example that may be marginally useful but doesn't add critical information. Still, it's well-front-loaded and wastes no words.

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

Completeness3/5

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

As a simple one-parameter tool with no output schema, the description covers the minimum: what it does and an example. However, it does not specify the return format or scope of 'quote data', leaving some ambiguity. Adequate but not comprehensive.

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 coverage is 100%, so baseline 3. The description reiterates the schema's parameter meaning ('stock symbol') and gives an example, but adds no additional semantic value beyond what the schema already provides.

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?

The description clearly states the action ('Fetches'), resource ('latest quote data'), and context ('for a provided stock symbol from Google Finance'). It effectively distinguishes the quote-fetching tool from sibling tools like google_finance_ticker or google_finance_company.

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?

No guidance on when to use this tool versus alternatives (e.g., google_finance_ticker for detailed info, other finance tools for different data). The description lacks exclusions or context about its niche within the finance tool family.

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