Skip to main content
Glama
Sign In
yfinance-ai MCP server

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_analyst_recommendations

Read-onlyIdempotent

Fetch analyst buy, hold, and sell recommendations, consensus ratings, and recent upgrades or downgrades for a given stock ticker.

Instructions

Get analyst recommendations and ratings.

Args: ticker: Stock ticker symbol

Returns: Analyst buy/hold/sell recommendations, consensus, and recent upgrades/downgrades

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_analyst_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only mild behavioral context by naming the data categories returned (recommendations, consensus, upgrades/downgrades); it says nothing about freshness, coverage, or rate limits beyond that.

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?

The Args/Returns layout is front-loaded and easy to scan, and the whole thing is short. The Returns block is somewhat redundant given an output schema exists, but nothing is bloated or buried.

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 an output schema present, the description needn't explain return values, yet that is where most of its words go. For a simple one-parameter tool it is minimally sufficient, but it omits the sibling disambiguation that would actually help an agent call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single parameter, so the description must carry the load. It offers only 'ticker: Stock ticker symbol', which essentially restates the schema title 'Ticker' with no format, case, exchange-suffix, or validation guidance.

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 ('Get analyst recommendations and ratings') and enumerates the returned content (buy/hold/sell, consensus, upgrades/downgrades). It does not distinguish itself from close siblings like get_upgrades_downgrades, get_analyst_estimates, or get_analyst_price_targets, so an agent cannot route confidently among them.

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?

No when-to-use, when-not-to-use, or alternative guidance appears anywhere in the description. This matters here because the stated return content ('recent upgrades/downgrades') directly overlaps a sibling tool named get_upgrades_downgrades, and the description never explains which to pick.

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