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

yfinance-ai MCP server

by lkcair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_eps_revisions

Read-onlyIdempotent

Fetch analyst EPS estimate revisions for a ticker to track upward or downward changes in earnings expectations.

Instructions

Get EPS revision data showing analyst estimate changes.

Args: ticker: Stock ticker symbol

Returns: EPS revisions showing up/down estimate changes by analysts

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_eps_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds essentially nothing beyond that: no auth requirements, no coverage universe, no rate limits, and its return-value note duplicates the output schema.

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

Conciseness3/5

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

The core sentence is front-loaded and short, but the 'Args/Returns' scaffolding is largely redundant: the parameter is already in the input schema and the return content is already described by the existing output schema. Roughly a third of the text earns no new information.

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 a rich annotation set and an output schema present, the description need not explain returns or safety, and it is adequate for a single-parameter read tool. Its real gap is routing: nothing tells the agent why to pick this over get_eps_trend or get_analyst_estimates in a 70-tool catalog.

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 0% (the single param carries only the title 'Ticker'), so the description must compensate, and 'ticker: Stock ticker symbol' is the minimum it can do. It does not specify expected format (e.g., 'AAPL' vs. exchange-suffixed symbols), though with only one obvious parameter the risk of misuse is low.

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 EPS revision data showing analyst estimate changes,' which tells an agent exactly what comes back (up/down analyst estimate changes). However, it offers no differentiation from close siblings like get_eps_trend, get_analyst_estimates, or get_upgrades_downgrades, so the agent must guess which is correct.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many overlapping analyst-estimate siblings. The agent is left to infer that this is the estimate-revision view rather than the trend or estimates view.

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