Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_ticker_analysts

Retrieve Yahoo Finance analyst data for a stock symbol, including recommendation trends, upgrade/downgrade history, price targets, and estimates.

Instructions

Yahoo Finance analyst data. Returns analyst data for a Yahoo Finance symbol such as AAPL, as modules keyed by Yahoo module name: recommendation trend, upgrade and downgrade history, price targets and estimates, where Yahoo provides them.

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
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape (modules keyed by Yahoo module name) and hedges availability with 'where Yahoo provides them,' but says nothing about read-only safety, permissions, or rate limits. Some value added, notable gaps remain.

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?

Two tightly written sentences with the resource and its contents front-loaded. Every clause earns its place, though the leading fragment 'Yahoo Finance analyst data' is slightly redundant with the sentence that follows.

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?

With no output schema, the description must convey return values — and it does, describing the modules structure and the four content categories. For a single-parameter read tool this is nearly complete; only the safety/availability profile is thin.

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% and there is a single required parameter already documented in the schema ('Yahoo Finance symbol such as AAPL'). The description merely restates the symbol format, adding no syntax or meaning beyond the schema. 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?

The description gives a specific verb and resource ('Returns analyst data') and enumerates the exact contents: recommendation trend, upgrade/downgrade history, price targets and estimates. This content listing implicitly distinguishes it from siblings like yahoo_finance_ticker_holders or yahoo_finance_ticker_quote, though it never names an alternative explicitly.

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?

Usage is implied by the tool's scope (pull analyst sentiment/estimates for a symbol), and the caveat 'where Yahoo provides them' hints that data may be absent for some symbols. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidelines fall to the minimum viable level.

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