Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_analyst_articles

Retrieve Google Finance analyst articles for a stock quote like AAPL:NASDAQ. Returns titles, sources, URLs, and publication times when available.

Instructions

Google Finance analyst articles. Returns the analyst articles Google Finance shows for a quote such as AAPL:NASDAQ. Each article has its title, source, URL, publication time (ISO and Unix), thumbnail and the related instruments with price, change and exchange. Articles come back only when Google Finance has them for that quote.

Input Schema

NameRequiredDescriptionDefault
quoteYesQuote identifier such as AAPL:NASDAQ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the exact return contents (title, source, URL, ISO/Unix pub time, thumbnail, related instruments) and an important behavioral caveat that results are conditional on Google Finance coverage. No permission, rate-limit, or pagination details, but solid for a read tool.

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?

Four short sentences, front-loaded with the resource name and scope before the return-shape details. No padding, though the field enumeration is slightly list-like.

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?

No output schema exists, so the description must describe returns, and it does so thoroughly, including the conditional-coverage caveat. Complete enough for an agent to call and interpret this tool.

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?

Only one parameter with 100% schema description coverage, so the schema already documents the quote format. The description's AAPL:NASDAQ example duplicates the schema's own example, adding no new meaning beyond the baseline.

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+resource (return analyst articles shown for a quote) and names the source, Google Finance. An agent can distinguish it from siblings like google_finance_news or google_finance_quote without inspecting schemas.

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 the required quote parameter and the caveat that articles only appear when Google Finance has them for that quote. However, it never names alternatives (e.g. general news) or states when-not to use it, so routing guidance is only inferable.

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