Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_finance_markets_featured

Fetch the stocks featured on Google Finance markets, including ticker, exchange, price, change, previous close, currency, country, time zone, and after-hours data.

Instructions

Google Finance featured stocks. Returns the stocks Google Finance features on its markets page. Each instrument has its ticker, exchange, name, price, change and change percent, previous close, currency, country, time zone and after-hours data.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/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 disclose the return shape (ticker, exchange, name, price, change, change percent, previous close, currency, country, time zone, after-hours data). However it omits operational traits such as how many instruments are returned, whether the list is region-scoped, and refresh/pagination behavior.

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 tight sentences, front-loaded with the core purpose and then the field inventory. No filler or redundancy; the field list is the longest part but it earns its place given there is no output schema.

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 zero-parameter list tool the description is nearly sufficient, and the field enumeration compensates for the missing output schema. What is missing is any routing context: in a family of ~20 google_finance_markets_* tools, an agent cannot tell from this text why it would pick 'featured' over 'top', 'trending', or 'movers'.

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 the schema baseline of 4 applies. There is nothing further the description could add on parameter semantics.

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: it returns the stocks Google Finance features on its markets page. The purpose is unambiguous, though it does not differentiate itself from close siblings like google_finance_markets_top or google_finance_markets_trending, which plausibly return similar featured/ranked stock lists.

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 markets endpoints (top, trending, movers, indices). The word 'featured' implies a default/curated list but no condition or alternative is named.

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