Skip to main content
Glama

FinanceQuery

Price Target Consensus

get_price_target_consensus
Read-onlyIdempotent

Get a stock's consensus analyst price target (high/low/mean/median).

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the shape of the returned consensus (high/low/mean/median), which is genuine value given there is no output schema, but says nothing about data freshness, the number of contributing analysts, or what happens for an uncovered symbol.

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?

A single sentence with zero filler, front-loaded with the action and immediately followed by the specific metrics returned. Nothing is redundant with the title or the schema.

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?

For a simple two-parameter read tool with annotations and full schema coverage, the description is broadly sufficient and even compensates for the missing output schema by naming the return fields. It falls short on realistic edge cases — no analyst coverage, currency, or staleness of consensus figures — which matter for a financial data lookup.

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%, with both symbol ('Stock ticker symbol') and fields ('Comma-separated list of GraphQL field names') documented inline. The description adds no extra meaning about either parameter, so the baseline 3 applies; in particular the non-obvious GraphQL field-selection parameter is left entirely to the schema.

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 a stock's consensus analyst price target') and enumerates the returned statistics (high/low/mean/median), so the agent knows exactly what data comes back. It does not, however, distinguish itself from close siblings like get_price_target_summary or get_rating_consensus, which an agent could easily confuse it with.

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 or when-not-to-use guidance, and no mention of prerequisites such as needing a valid ticker with analyst coverage. With a sibling named get_price_target_summary in the catalog, the absence of any routing hint leaves the selection decision entirely to inference.

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.