finstack-mcp

credit_ratings

Retrieve credit ratings for Indian listed companies from SEBI-mandated exchange filings. Includes rating agency, current rating, rating action, instrument type, rated amount, outlook, and filing date.

Instructions

Credit ratings for an Indian listed company from SEBI-mandated exchange filings.

SEBI requires all rated instruments to disclose credit rating changes on NSE/BSE. Bloomberg charges $24,000/year to access this. SEBI makes it public. We surface it free.

Provides:

Rating agency (CRISIL, ICRA, CARE, India Ratings)
Current rating and rating action (upgraded/downgraded/reaffirmed)
Instrument type and rated amount
Outlook (stable/positive/negative/watch)
Filing date

Args: symbol: NSE stock symbol (e.g., RELIANCE, TATAMOTORS, ADANIENT)

Examples: credit_ratings("RELIANCE") → Reliance credit ratings from CRISIL/ICRA credit_ratings("ADANIENT") → Adani credit rating history and current outlook

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

Input Schema

Name	Required	Description	Default
`symbol`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedApr 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the data source, the fields returned, and the fact that it is free. It does not mention error handling, data freshness, or potential limitations, but for a simple read-only retrieval tool this is largely sufficient.

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 well-structured with an introduction, bullet list of outputs, args, and examples. The Bloomberg pricing detail adds context but is not essential for tool invocation, making it slightly less concise than necessary.

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?

For a single-parameter tool with an output schema, the description provides all necessary context: purpose, input format, examples, and output fields. It is complete enough for an agent to select and invoke the tool accurately.

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

Parameters5/5

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

The only parameter, symbol, is fully defined in the description as an NSE stock symbol with concrete examples. The input schema provides only the parameter name and type, so the description adds necessary context and usage syntax.

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?

Clearly states the tool provides credit ratings for Indian listed companies from SEBI-mandated exchange filings. Lists specific data fields (agency, rating, action, instrument, outlook, filing date), which distinguishes it from all sibling tools focused on quotes, financials, and market data.

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?

Specifies input as NSE stock symbol and provides examples for RELIANCE and ADANIENT. The description implies use when credit rating information is needed, and the uniqueness of the tool among siblings removes ambiguity. It does not explicitly mention alternative tools or when not to use it.

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

Deploy Server