Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

peer_comparison

Read-only

Compares a stock's valuation ratios with its industry aggregate side by side to help judge whether a ratio is cheap or expensive relative to peers.

Instructions

A stock's valuation ratios AND its INDUSTRY aggregate, side by side. This is the denominator that absolute valuation bands do not have: 'PBV 1.2' is expensive for a bank and cheap for a consumer name, and the analyze tool's valuation pillar scores against fixed bands and says in its own output that this is systematically wrong for banks, property and cyclicals. Use this tool before calling any ratio cheap or expensive. Which number is which is never ambiguous: in paired, symbolValue is the company you asked about and industryValue is Stockbit's aggregate for its industry. symbolOnly and industryOnly are metrics that exist on one side only, so there is nothing to compare them with. otherCompanies holds rows the payload attributed to a DIFFERENT ticker — the peer set, not the subject — and they are deliberately excluded from the pairing. NO VERDICT IS COMPUTED. These are Stockbit's numbers placed next to each other; the judgement is yours, and 'below the industry' is not by itself a reason to buy anything. PENDING: the comparison response shapes are unverified, so the pairing is a best-effort match on label TEXT rather than a mapped schema. Every reading records the wire key it came from (labelKey/valueKey) and its path inside raw, so check a pair before relying on it. A label that matched more than one reading on a side is listed under ambiguous with all its candidates instead of being paired arbitrarily. If paired is empty, that is a shape problem and the raw payloads are attached — it is not a statement about the company. include_catalogues adds the comparison metric vocabulary and the account's saved comparison sets. It costs two extra requests and answers 'what can be compared', not 'how does this company compare', so leave it off unless that is the question.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBRI
include_rawNoKeep the unprojected payloads under `raw` (default true; set false if too large)
include_cataloguesNoAlso fetch the comparison metric list and saved comparison sets (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Despite annotations already covering the read-only/open-world profile, the description adds substantial behavior: no verdict is computed, pairing is best-effort on label TEXT because response shapes are unverified, ambiguous labels are surfaced under `ambiguous` rather than paired arbitrarily, and an empty `paired` is a shape problem rather than a statement about the company. The only thing not disclosed is roughly how large/verbose the payload is beyond the `include_raw` size warning.

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 value proposition before the caveats, and the field-by-field section is scannable. It is long and dense, and a few clauses (the repeated 'deliberately excluded from the pairing' justification) could be tightened, but almost every sentence carries operational weight.

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 full burden of explaining the return shape and does so: `paired` with `symbolValue`/`industryValue`, `symbolOnly`/`industryOnly` for one-sided metrics, `otherCompanies` for peer-set rows, `ambiguous`, and `raw` with `labelKey`/`valueKey` provenance. An agent knows how to read the result and how to validate a pairing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the cost of `include_catalogues` (two extra requests) and the question it answers, and ties `include_raw` to the `raw` path and its use in diagnosing empty pairings.

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?

States a specific resource and operation: a stock's valuation ratios paired with its industry aggregate, framed as 'the denominator that absolute valuation bands do not have.' It explicitly contrasts itself with the `analyze` tool's fixed-band valuation pillar, so an agent can tell them apart without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use this tool before calling any ratio cheap or expensive') plus a concrete motivating example (PBV 1.2 for a bank vs a consumer name). It also gives a when-not rule for the optional flag: leave `include_catalogues` off unless the question is 'what can be compared' rather than 'how does this company compare.'

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