Skip to main content
Glama
screener-mcp
by LogeshR15

get_analyst_targets

Read-only

Fetch analyst price targets for a stock from consensus data and recent news-cited broker targets, including implied upside, rating splits, and source links.

Instructions

Analyst price targets for a stock, from two independent sources:

  1. Consensus (Yahoo Finance): mean / median / high / low target, number of analysts, implied upside vs the current price, and the strong-buy/buy/hold/sell/strong-sell split.

  2. Broker targets mentioned in the last 60 days of news headlines (e.g. "ICICI Securities target ₹370"), with links to each article.

The two come from different broker sets and dates, so they rarely match; both are labelled with their source. Returns partial=true if one source is unavailable, or if the stock has no analyst coverage.

symbol: NSE/BSE symbol or company name

Examples: get_analyst_targets("TMPV") get_analyst_targets("HDFCBANK")

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": {
      "symbol": "<symbol>"
    },
    "name": "get_analyst_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the 60-day news window for broker targets, the fact that the two sources come from different broker sets and dates so they rarely agree, and that partial=true is returned when a source is unavailable or coverage is absent. It does not discuss rate limits or freshness of the consensus snapshot, which keeps it from a 5.

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?

Numbered source breakdown, a clear caveat paragraph, a labelled parameter line, and short examples — every element is front-loaded and functional. The explanation of what each source yields is necessary to interpret the output, so it earns its space rather than repeating the tool name.

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

Completeness5/5

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

For a single-parameter read tool with an output schema, this is complete: the agent knows what data is returned, that results are source-labelled, and how to interpret partial results. Combined with readOnlyHint annotations, nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the parameter alone, and it does: 'symbol: NSE/BSE symbol or company name' clarifies the accepted identifier forms, and the two examples ('TMPV', 'HDFCBANK') demonstrate the expected casing and format. That is meaningfully more than the bare string schema, though it stops short of saying whether company names are resolved by exact match or fuzzy search.

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 states a specific resource (analyst price targets for a stock) and immediately enumerates the two distinct sources it draws from: Yahoo Finance consensus aggregates and broker targets mined from recent news. This clearly separates it from siblings like get_recent_news or get_relative_valuation, which touch adjacent data but answer different questions.

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 content — an agent reading it knows this is the tool for target prices — and the note that the two sources 'rarely match' helps set expectations. However, there is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative for related questions (e.g., valuation context or recent news).

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