Skip to main content
Glama

FinanceQuery

Analyst Data

get_analysis
Read-onlyIdempotent

Get analyst data for a stock: recommendation trends, upgrades/downgrades, earnings estimates, or earnings history.

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>",
      "analysis_type": "<analysis_type>"
    },
    "name": "get_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol
analysis_typeYesAnalysis type: recommendations | upgrades-downgrades | earnings-estimate | earnings-history

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond the content enumeration: nothing about data source freshness, market coverage, or how large a response to expect.

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?

One front-loaded sentence with no filler; the core verb comes first and the variants follow. The only weakness is that 'analyst data' is a vague umbrella term that only becomes concrete at the end of the sentence.

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 three-parameter read tool with full schema coverage, complete annotations, and no output schema, the description is minimally adequate. It does not tell the agent what the returned records look like beyond the category names, nor how required symbol/analysis_type interact.

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%, covering symbol, analysis_type values, and the fields override, so the baseline is 3. The description restates the analysis_type variants (slightly mismatched in casing/hyphenation: 'earnings estimates' vs 'earnings-estimate') but adds no meaning about the fields parameter or required-vs-optional behavior.

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?

Names a specific verb and resource ('Get analyst data for a stock') and enumerates the four analysis flavors (recommendation trends, upgrades/downgrades, earnings estimates, earnings history), which lets an agent distinguish it from siblings like get_earnings_surprises or get_earnings_transcript. It stops short of stating explicitly how it differs from those neighboring tools.

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?

The list of analysis types implicitly tells the agent what content can be requested, which is the main routing cue. There is no explicit when-to-use/when-not-use guidance and no mention of alternatives for overlapping data (e.g., earnings surprises vs earnings history).

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.