Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Analyst consensus

financial_analyst_consensus
Read-onlyIdempotent

Retrieve analyst rating consensus and target price for a stock symbol to assess market sentiment and valuation expectations.

Instructions

Consensus of analyst ratings and target price for one symbol.

Returns (Stockbit's data field): data[{title|name, items[{year, value, label, is_estimate}]}] (empty array when no coverage)

Paywall: unknown.

Endpoint: GET exodus /analyst-ratings/{symbol}/consensus.

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": "financial_analyst_consensus"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description does add real context beyond them: the returned data shape, the empty-array case when there is no coverage, and an explicit 'Paywall: unknown' caveat. However, 'Paywall: unknown' flags a risk without resolving it, leaving the agent unable to predict whether the call will succeed.

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?

Front-loaded purpose sentence, then return shape, then caveat, then endpoint — easy to scan with no filler. Minor redundancy in labeling the payload as 'Stockbit's data field'.

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?

No output schema exists, and the description compensates by spelling out the response structure and the empty-array edge case. The one real gap is that paywall/access status is left as 'unknown', so the agent cannot know the auth or subscription requirements.

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?

With one parameter and 100% schema description coverage ('IDX ticker, e.g. BBCA'), the schema already carries the semantics. The description only restates 'for one symbol' and adds no format, market, or casing detail beyond 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+resource: consensus of analyst ratings and target price for one symbol. Clear on its own, but it never distinguishes itself from the very similar sibling financial_analyst_ratings, so an agent cannot tell the two apart from this text alone.

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?

Provides no when-to-use, when-not-to-use, or alternative guidance. The only scoping hint is 'for one symbol', which is implied by the single-symbol schema rather than stated as a usage rule.

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