Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_markets_top

List top Google Finance instruments by ranking metric with pagination. Retrieve ticker, exchange, name, price, change, change percent, and previous close for each result.

Instructions

Google Finance top stocks by metric. Lists the top Google Finance instruments for a ranking metric. metric is a Google Finance metric id (default 6) and page is the page number (default 1). Each item has its ticker, exchange, name, price, change and change percent, and previous close.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
metricNoGoogle Finance metric id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden. It does add real value by enumerating the returned fields (ticker, exchange, name, price, change, change percent, previous close) with no output schema present. It says nothing about authentication, rate limits, or how paging behaves at the end of the list, which leaves notable gaps for a no-annotation 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?

Three short sentences, front-loaded with the purpose before parameters and return shape. There is little waste, though the return-field sentence is a somewhat dense run-on list.

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?

With no output schema and no annotations, the description does cover the return fields and both parameters, which is more than many peers. It still omits the meaning/range of metric ids, total page behavior, and any safety or permission context, so it is adequate but not complete.

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 baseline is 3. The description modestly exceeds the terse schema descriptions ('Page number', 'Google Finance metric id') by supplying the default values 6 and 1, but it never explains what metric ids denote or what values are valid, so the added meaning is limited.

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 names a specific resource and action: 'Lists the top Google Finance instruments for a ranking metric,' which is clear enough to distinguish it from a plain quote or search tool. It does not, however, explicitly differentiate itself from close siblings like google_finance_markets_movers, google_finance_markets_trending, or google_finance_markets_indices, so an agent must infer which ranking tool to pick.

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 guidance and no mention of alternatives. The description never says what distinguishes this metric-ranked list from google_finance_markets_movers or google_finance_markets_trending, nor when ranking by metric is the right choice. Usage is only implied by 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