Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_markets_movers

List Google Finance market movers by numeric category, with ticker, exchange, name, price, change, change percent, and previous close. Set count or offset to page results.

Instructions

Google Finance market movers. Lists Google Finance market movers. categories takes comma-separated numeric categories, count sets how many items to return (default 20) and offset skips ahead. Each item has its ticker, exchange, name, price, change and change percent, and previous close.

Input Schema

NameRequiredDescriptionDefault
countNoResult count
offsetNoResult offset
categoriesNoComma-separated numeric categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the shape of each returned item (ticker, exchange, name, price, change, change percent, previous close), which is valuable since there is no output schema, but it says nothing about authentication, rate limits, or whether results are stable/repeatable. Read-only listing behavior is implied by "Lists" rather than stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first two sentences are redundant — "Google Finance market movers. Lists Google Finance market movers." — wasting the most prominent position. The remainder is dense and useful, but the lead-in repetition drags the structure down.

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?

For a simple listing tool with no annotations and no output schema, the description covers the return fields and pagination parameters reasonably well. However, it omits any indication of the category value space and provides no routing among the numerous google_finance_markets_* siblings, leaving the agent under-equipped to choose correctly.

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 the schema already documents all three parameters. The description adds only one genuinely new fact (count defaults to 20) and otherwise restates the schema ("comma-separated numeric categories" verbatim; "offset skips ahead"). Critically, it never explains what the numeric category values mean, which is the main semantic gap.

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 specific verb and resource ("Lists Google Finance market movers"), so an agent knows it retrieves a ranked list of market movers. It does not, however, distinguish this from close siblings such as google_finance_markets_top, google_finance_markets_trending, or google_finance_markets_featured, which appear to be adjacent listing endpoints.

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 guidance on when to use this tool versus the many sibling market endpoints, and no prerequisites or context conditions are stated. The agent must infer usage entirely from the name.

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