Skip to main content
Glama
india-markets-mcp

india-markets-mcp

Compare Fundamentals

compare_fundamentals

Compare valuation fundamentals for 2–10 Indian stock symbols side by side, ranked by trailing P/E to surface lower-valuation candidates.

Instructions

Side-by-side valuation of 2-10 symbols, cheapest trailing P/E first.

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": {
      "symbols": "<symbols>"
    },
    "name": "compare_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behaviors: the 2-10 symbol range and the result ordering (cheapest trailing P/E first). It is silent on whether the call is read-only, what happens outside the range (error vs. truncation), and which valuation metrics beyond trailing P/E are returned.

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 sentence, front-loaded with the operation and scoped with the range and sort behavior; nothing is padded or repeated from the title.

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?

For a single-parameter tool with an output schema (so return values need no explanation), the description covers domain, input bounds, and output ordering. The remaining gap is sibling disambiguation, which matters here given several overlapping comparison tools.

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 0% and the single parameter is an untyped-strings array, so the description's "2-10 symbols" bound is genuinely additive — it supplies cardinality limits the schema lacks. It does not specify symbol format (ticker casing, exchange prefixes), leaving one gap.

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?

"Side-by-side valuation of 2-10 symbols" states the operation (valuation comparison) and scope (2-10 symbols) rather than merely restating the name. It never distinguishes itself from the sibling compare_symbols or get_fundamentals, so an agent cannot tell from the text which comparison surface to choose.

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?

No when-to-use, when-not-to-use, or alternative is named despite three adjacent siblings (compare_symbols, get_fundamentals, sector_peers) that plausibly overlap. The only usage signal is the implicit 2-10 symbol range, which constrains input rather than routing the agent.

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