Skip to main content
Glama
Signal8 MCP Server

Signal8 MCP Server

Official

Get Analyst Consensus

get_analyst_consensus
Read-only

Fetch analyst ratings consensus for a company, including average target price, analyst count, buy/hold/sell breakdown, and recommendation to assess market sentiment.

Instructions

Get the analyst ratings consensus for a company: average target price, number of analysts, buy/hold/sell breakdown and consensus recommendation.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_analyst_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only a summary of the returned fields, with no notes on data freshness, coverage limits, or behavior for tickers with no analyst coverage. With a rich output schema present, this level of added context is adequate but not substantial.

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 that leads with the verb and resource, then lists the payload. The field enumeration partly overlaps with the output schema, which is mild redundancy, but nothing is padded or unclear.

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 annotations covering safety and an output schema covering return shape, the description supplies the one thing structured fields can't: a human-readable statement of what the consensus payload contains. Its only real omission is routing guidance within the crowded analyst-tool family.

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?

There is a single required ticker parameter with 100% schema description coverage, so the schema fully documents it. The description adds no format or edge-case guidance (e.g., exchange-qualified symbols, case sensitivity) beyond the schema, which matches the baseline for high-coverage schemas.

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 and resource ('Get the analyst ratings consensus for a company') and enumerates what the result contains: average target price, analyst count, buy/hold/sell breakdown, and recommendation. It does not distinguish itself from close siblings such as get_analyst_coverage, get_analyst_grades, get_analyst_estimates, or get_price_target, so differentiation is left to the agent.

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 explicit guidance on when to choose this over the several analyst-related siblings, nor any stated prerequisites beyond needing a ticker. Usage is only inferable from the tool name and the word 'consensus'.

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

Deploy Server

Other Tools