Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

google_finance_markets_headline

Fetches the top markets headline from Google Finance as one article with title, source, URL, timestamps, thumbnail, and related instrument prices; returns data only when a headline exists.

Instructions

Google Finance top headline. Returns the top headline on Google Finance markets as one article: title, source, URL, publication time (ISO and Unix), thumbnail and the related instruments with price and change. The article is present only when Google Finance shows a headline.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does well by enumerating the returned fields: title, source, URL, publication time formats, thumbnail, and related instruments with price and change. It also discloses the important edge case that the article is present only when Google Finance shows a headline, implying the result can be absent. It does not cover auth or rate-limit behavior, but for a simple read tool this is solid transparency.

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?

The description is front-loaded with a short identifying statement, then one sentence enumerating the return shape, followed by a conditional note. It is efficient and every sentence adds useful information, though the opening fragment is slightly informal.

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 no-parameter, no-output-schema retrieval tool, the description adequately explains what is returned and when the result may be absent. No annotations exist, so the description must cover behavioral and return context, which it largely does. Sibling differentiation is the main omission.

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?

The tool takes zero parameters, so there is nothing for the description to clarify beyond the schema. Baseline for a parameterless tool is 4.

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?

The description states a clear verb and resource: it returns the top headline on Google Finance markets as a single article. It is specific enough that an agent can distinguish it from broader news tools, but it does not name or differentiate against close siblings like google_finance_markets_top or google_finance_news.

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 provides no explicit when-to-use guidance, no alternatives to consider, and no prerequisites. It only notes a data-availability condition, which is useful but not usage guidance in the sense of selecting this tool over another.

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