Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_markets_trending

Discover currently trending stocks directly from Google Finance. Access detailed financial data, including ticker, price, change, and exchange information for top instruments.

Instructions

Google Finance trending stocks. Returns the instruments currently trending on Google Finance, up to limit items (default 18). Each has its ticker, exchange, name, price, change and change percent, previous close, currency and after-hours data.

Input Schema

NameRequiredDescriptionDefault
limitNoResult limit

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?

No annotations are provided, so the description carries the full burden, and it does disclose the returned fields (ticker, exchange, name, price, change, change percent, previous close, currency, after-hours) and the default result count of 18. It omits pagination behavior and any rate/auth context, but for a read-only listing tool the return-content disclosure 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the tool's identity followed by return details. There is slight redundancy between 'Google Finance trending stocks' and 'currently trending on Google Finance', but overall it is efficient with no filler.

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-annotation, no-output-schema read tool, the description supplies the return shape and default limit, which is enough to call it correctly. The main gap is not clarifying its relationship to the overlapping markets_movers/markets_top siblings.

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% for the single 'limit' parameter, so the baseline is 3; the description goes beyond the schema by supplying the default value (18), which the schema does not state. That default is the key semantic detail an agent needs to reason about call behavior.

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 instruments currently trending on Google Finance'), so the agent knows it lists trending instruments. However, it does not distinguish itself from the many similarly-named siblings such as google_finance_markets_movers, google_finance_markets_top, and google_finance_markets_featured, leaving the agent to guess at the boundary.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. With siblings like movers/top/featured/indices that overlap conceptually, an explicit routing hint would be valuable and is absent.

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