Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_news

Retrieve recent Google Finance news for a stock quote like AAPL:NASDAQ. Set a limit and get article titles, sources, URLs, publication times, thumbnails, and related quote price changes.

Instructions

Google Finance quote news. Returns recent Google Finance news for one quote, such as AAPL:NASDAQ, given in the quote path parameter. limit caps the number of articles and defaults to 6. Each article has its title, source, URL, publication time (ISO and Unix), thumbnail, and related quotes with price and change data.

Input Schema

NameRequiredDescriptionDefault
limitNoArticle limit
quoteYesQuote identifier such as AAPL:NASDAQ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the returned fields (title, source, URL, publication time in ISO and Unix, thumbnail, related quotes with price/change) and the default limit of 6. It does not cover pagination or rate limits, but for a read-only news endpoint this is solid.

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 purpose then parameter behavior then return shape. No filler or repetition.

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?

Since there is no output schema, the description usefully enumerates the article fields, giving the agent enough to know what comes back. Minor gaps remain around ordering/recency guarantees and any failure modes for bad quote identifiers.

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 the default value of `limit` (6) and reiterates the quote format with an example, which the schema only partially conveys. It meaningfully clarifies both parameters beyond the schema text.

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 and resource (returns Google Finance news) scoped to a single quote, with a concrete example identifier. It is distinguishable from siblings like google_finance_markets_category_news or google_news, which cover broader or non-quote news.

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 by 'for one quote, such as AAPL:NASDAQ', so an agent can infer it needs a ticker-style identifier. However, it never states when to prefer this over the many other finance/news siblings, nor any prerequisites for obtaining the quote format.

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