Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_valuation

Fetch Yahoo Finance valuation measures for a stock symbol such as AAPL, returning key statistics as headers and rows keyed by column.

Instructions

Yahoo Finance valuation measures. Returns the valuation measures table from Yahoo Finance key statistics for a symbol such as AAPL, as headers and rows keyed by column, for example Market Cap. Returns an upstream error when Yahoo does not serve the table.

Input Schema

NameRequiredDescriptionDefault
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/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 real behavior: the return shape as `headers` and `rows` keyed by column, and the explicit failure mode of an upstream error when Yahoo does not serve the table. It omits auth/rate-limit context, but for a read-only fetch this is solid disclosure.

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 what is returned, then output shape, then failure mode. The opening sentence lightly restates the tool name, but otherwise every sentence earns its place.

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 one-parameter read tool with no output schema and no annotations, the description covers purpose, return structure, and error behavior adequately. It could be more complete by distinguishing itself from the numerous sibling ticker endpoints.

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%, so the single `symbol` parameter is already documented. The description's example (`AAPL`) duplicates the schema's example, adding no new meaning. Baseline 3 is appropriate.

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 (returns) and resource (the valuation measures table from Yahoo Finance key statistics), scoped by `symbol`. It is clearly distinguishable from siblings like ticker_financials or ticker_info by naming the exact table, though it does not explicitly contrast with those siblings.

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?

Gives no when-to-use guidance and names no alternatives among the many yahoo_finance_ticker_* siblings. Only an implied context (key statistics valuation table) tells the agent when this is the right call.

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