Skip to main content
Glama

FinanceQuery

Price Target Summary

get_price_target_summary
Read-onlyIdempotent

Get analyst price-target counts and averages per window (FMP only, requires FMP_API_KEY).

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 fully covered. The description adds genuinely useful behavior context beyond that — this is an FMP-only data source requiring FMP_API_KEY, so the agent knows it may fail without credentials — but says nothing about what 'window' means, rate limits, or error behavior when the key is absent.

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?

A single front-loaded sentence with the core purpose first and the provider/credential caveat in parentheses; no wasted wording. The parenthetical is dense but does earn its place by flagging a hard precondition.

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 no output schema, the description carries the burden of explaining return shape, and it does so only at a high level ('counts and averages per window') without clarifying what windows exist or how many rows come back. For a simple two-parameter read tool this is adequate but leaves the agent guessing about the response structure.

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%, so both the symbol and the fields parameters are already documented in the schema. The description adds only the notion of 'per window', and notably introduces a window concept that has no corresponding parameter, which slightly muddies rather than clarifies the parameter model. Baseline 3 applies.

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 price-target counts and averages per window', which is concrete enough that an agent knows it returns aggregated counts and averages rather than individual targets or a single consensus number. It does not explicitly differentiate itself from the sibling get_price_target_consensus, so it falls short of a 5.

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 rather than stated: 'FMP only, requires FMP_API_KEY' tells the agent when the tool will work at all, which is a meaningful precondition. However, there is no guidance on when to pick this over get_price_target_consensus or other analysis tools, and no exclusions are given.

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.