Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

yahoo_finance_market_summary

Access Yahoo Finance market summary rows for a specified market to view key financial indicators.

Instructions

Returns Yahoo Finance market summary rows for a market such as US.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesMarket such as US
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states it returns rows, without disclosing read-only nature, data freshness, rate limits, or what exactly 'market summary rows' contain. This is insufficient for an AI agent.

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

Conciseness5/5

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

The description is extremely concise, consisting of one sentence. It is front-loaded with the action 'Returns', contains no fluff, and every part serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description is too minimal. It fails to explain what the rows represent, how to interpret the data, or any limitations. For an AI agent integrating with many similar tools, more context is needed.

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 description coverage is 100% with one parameter 'market' described as 'Market such as US', which echoes the tool description. The description adds no additional meaning beyond the schema, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns Yahoo Finance market summary rows for a specified market, using a specific verb and resource. It distinguishes from siblings like yahoo_finance_market_status which returns market status, and other data retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an example market 'US', implying usage context, but offers no guidance on when to use this tool versus alternatives like yahoo_finance_screener or google_finance_markets_*. No exclusions or alternative suggestions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server