Skip to main content
Glama

Analyst Price Targets

analyst_price_targets
Read-onlyIdempotent

Analyst price-target consensus for one US stock: mean, high and low target, the buy/hold/sell analyst counts, and about 13 months of month-by-month consensus history (mean target, rating split, and the high/avg/low band for the latest month). Use for "what is the Street price target on AAPL", "how has the AAPL target moved this year". Sourced live from Nasdaq's public analyst data.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "AAPL"
    },
    "name": "analyst_price_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker symbol, e.g. "AAPL", "NVDA", "AMGN".

Output Schema

NameRequiredDescriptionDefault
idNo
sourceNo
symbolYes
historyYes
analysts_buyNo
retrieved_atNo
analysts_holdNo
analysts_sellNo
price_target_lowNo
price_target_highNo
price_target_meanYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the source (Nasdaq public analyst data) and the exact coverage window (~13 months of month-by-month history), which tells the agent how stale or deep the data is. No error or rate-limit behavior is mentioned.

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 content payload (what is returned) is front-loaded, then usage examples, then provenance. Dense but each clause carries information; the enumeration of returned fields is long but justified since it defines scope.

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 an output schema present, return-value explanation is unnecessary, and the description correctly focuses on scope, coverage window, and data source. For a single-parameter read-only lookup this is essentially complete; only a note on failure behavior for non-US or unknown tickers is missing.

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% and only one parameter exists, so the schema already carries the symbol semantics. The description reinforces the single-US-stock constraint but adds no syntax or validation detail beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific verb+resource (analyst price-target consensus) and enumerates exactly what is returned: mean/high/low target, buy/hold/sell counts, and ~13 months of consensus history. Scope is bounded to one US stock, which separates it in substance from ratings-only or forward-estimate siblings, though none are named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Two concrete example phrasings ("what is the Street price target on AAPL", "how has the AAPL target moved this year") make the intended trigger clear, including the trend/history use case. It stops short of saying when to prefer a sibling such as analyst_ratings_for_symbol or analyst_forward_estimates instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.