Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Analyst ratings

financial_analyst_ratings
Read-onlyIdempotent

Fetches broker analyst ratings and target prices for a stock symbol, returning buy/hold/sell counts plus best high and low price targets to gauge analyst consensus.

Instructions

Broker analyst ratings and target prices for one symbol.

Returns (Stockbit's data field): data{price_target{best_target, best_high_target, best_low_target, current_price}, recommendation{total_buy, total_hold, total_sell, ...}}

Paywall: unknown.

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

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

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely new context — the endpoint path and a paywall caveat (marked 'unknown', so of limited actionable value) — but says nothing about rate limits, data freshness, or what happens for symbols with no coverage.

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 with the core purpose in a single sentence, followed by clearly labelled Returns, Paywall and Endpoint blocks. Slightly technical/verbose for a one-parameter tool, but each block carries distinct information.

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 inline Returns block usefully names the key fields (price targets, buy/hold/sell counts), which is the description's main contribution. It is still incomplete on sibling differentiation and on what an empty/degraded response looks like, which matters for an external, open-world data call.

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?

Only one parameter, and the schema already documents it at 100% coverage including the IDX ticker example (BBCA). The description's 'for one symbol' adds nothing beyond the schema, so the 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?

"Broker analyst ratings and target prices for one symbol" states a specific resource (analyst ratings/target prices) and scope (single symbol), so the agent knows exactly what it retrieves. It does not, however, distinguish itself from the sibling financial_analyst_consensus, which an agent could reasonably 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?

The description gives no when-to-use guidance, no exclusions, and no reference to the closely related consensus tool. The only implied usage is 'one symbol at a time', which is already obvious from the required parameter.

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