Skip to main content
Glama
india-markets-mcp

india-markets-mcp

Sector Peers

sector_peers

Compare a large-cap stock’s P/E and P/B with illustrative same-sector peer medians to identify whether it trades at a premium.

Instructions

Compare a large-cap stock with illustrative same-sector peers: median P/E and P/B and its premium.

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

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does add one genuinely useful disclosure — that peers are "illustrative," i.e. a canned reference set rather than dynamically resolved comparables — but it says nothing about what happens for a non-large-cap or unrecognized symbol, nor about the reliability or vintage of the peer set. An output schema exists, so return values need not be described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One tight sentence with the subject and output metrics front-loaded and no filler. Nothing could be removed without losing substance.

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?

Because an output schema exists, the description's job is scope plus invocation guidance, and it covers scope well. The remaining gap — symbol format and edge-case behavior — is modest for a single-parameter read-only comparison tool.

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?

Schema coverage is 0% for the single 'symbol' parameter, so the description must compensate. It implies the symbol should denote a large-cap equity, which is meaning beyond the bare untyped string in the schema, but it never states the expected format (ticker vs. exchange-qualified) or how a non-large-cap symbol is handled.

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 concrete verb and resource — comparing a large-cap stock against same-sector peers — and specifies the metrics produced (median P/E, median P/B, and the stock's premium to those medians). That is specific enough to separate it from siblings like get_quote or compare_symbols, though it never explicitly contrasts itself with compare_fundamentals, which sounds closest in intent.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "large-cap stock" signals the applicable domain, but there is no wording about when to prefer this over compare_fundamentals or compare_symbols, and no statement of preconditions. An agent must infer applicability from the adjective alone.

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