Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

analyst_ratings

Read-only

Fetch per-analyst ratings and consensus for one IDX stock in a single call, including target price and buy/hold/sell counts. An empty result means no coverage, not a failure.

Instructions

What sell-side analysts publish on one IDX stock: the per-analyst rows AND the consensus roll-up (target price, buy/hold/sell counts), fetched together in one call. Analyst coverage on IDX is thin outside the large caps. An empty ratings or consensus means nobody publishes on that company, which is a real answer about a small-cap and NOT an error — do not retry it and do not report it as a failure. A request that genuinely failed is different: it appears in failed with its error kind, and the corresponding key is absent rather than empty. If both halves fail the tool errors instead of returning an empty-looking success. PENDING: neither response shape has been observed live, so both payloads are returned unprojected — read the target price and the rating counts out of them rather than expecting named fields. This reports what analysts said, not whether they were right, and nothing here is a 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": {
      "symbol": "<symbol>"
    },
    "name": "analyst_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBRI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare read-only, open-world, non-destructive, but the description goes much further: empty-vs-failed key semantics, the fact that both halves failing produces a tool error rather than an empty-looking success, and the PENDING warning that neither payload has been observed live so fields are unprojected and must be read out of raw maps. It also disclaims that this is a report of what analysts said, not a recommendation or an accuracy judgment.

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 highest-value sentence describing both halves, then ordered operational notes (empty vs failed, PENDING, disclaimer). Every paragraph earns its place relative to a tool with no output schema, though the PENDING narrative is slightly more expository than an agent strictly needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 does so: `ratings`, `consensus` (target price, rating counts), and `failed` with its error kind, plus the unprojected-payload caveat. For a one-parameter read tool that is complete enough to call and interpret correctly.

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 parameter, `symbol`, at 100% schema description coverage ('IDX ticker, e.g. BBRI'), so the schema already carries the meaning. The description adds no syntax, exchange, or format guidance for the ticker beyond the schema, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('what sell-side analysts publish on one IDX stock') and enumerates the two payload halves (per-analyst rows plus consensus roll-up with target price and buy/hold/sell counts) returned in one call. No sibling covers analyst ratings, so an agent can distinguish this from quote, keystats, or broker_summary on the resource alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear situational guidance: an empty `ratings` or `consensus` is a valid answer for thin IDX small-cap coverage, so the agent should not retry or report failure, and a genuine failure appears under `failed` instead. What it lacks is any explicit routing to an alternative tool when analyst data is not what the agent needs, so it stops short of a 5.

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