Skip to main content
Glama
india-markets-mcp

india-markets-mcp

Get Fundamentals

get_fundamentals

Retrieve a valuation snapshot for an Indian stock symbol, including market cap, P/E, P/B, ROE, debt/equity, dividend yield, and sector.

Instructions

Valuation snapshot: market cap (INR crore), P/E, P/B, ROE, debt/equity, dividend yield, sector.

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

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists return fields but does not state that this is a read-only operation, whether data is current or historical, or what the required symbol represents; the listing of fields is also redundant because an output schema exists.

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?

The description is a compact, front-loaded phrase with no wasted words. Its terseness is efficient, though the list format could be slightly clearer about the tool's action.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with one required parameter, no annotations, and an output schema, the description should at least cover the symbol input and basic usage context. It omits both, making it incomplete despite the simplicity of the tool.

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

Parameters2/5

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

The single required parameter, symbol, has 0% schema description coverage, and the description never mentions it. A single obvious parameter name provides some implicit meaning, but the description adds no explanation of what symbol should be or how it is used.

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 clearly states the resource: a valuation snapshot containing market cap, P/E, P/B, ROE, debt/equity, dividend yield, and sector. It lacks an explicit action verb and does not differentiate itself from siblings such as compare_fundamentals or get_quote, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives like compare_fundamentals, get_quote, or sector_peers. The description provides no context, exclusions, or prerequisites, leaving the agent to infer usage from the tool name alone.

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