Skip to main content
Glama

SMIFS Limited

Branches and grievance escalation

get_contact_and_grievance
Read-onlyIdempotent

SMIFS branch offices (city, address, phone, email) and the investor grievance escalation matrix (customer care, then each escalation level), plus the SEBI SCORES and SMART ODR routes. Optionally filter branches by city.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_contact_and_grievance"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOnly return branches in this city (for example "Mumbai").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds substance beyond that: it enumerates the returned branch fields and spells out the escalation ordering (customer care first, then each escalation level) plus external SEBI SCORES and SMART ODR routes. It does not discuss result volume, ordering, or whether branch data is static, which keeps it at 4.

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?

Two tight sentences, front-loading the two main data sets before the optional filter note. The parenthetical enumerations are dense but each conveys real content; nothing is redundant with the title or schema.

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?

With no output schema, the description carries the burden of describing returns, and it does list the branch fields and the structure of the escalation chain. Minor gaps remain, such as what fields the escalation entries contain and whether results are paginated, but an agent has enough to call it correctly.

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. The description adds genuine meaning by clarifying that the city filter is optional and that it applies only to branches, not to the grievance escalation matrix or the SEBI/ODR routes, which is not evident from the schema alone.

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?

Names the concrete resources retrieved: SMIFS branch offices with city/address/phone/email, the investor grievance escalation matrix, and the SEBI SCORES and SMART ODR routes. An agent can tell this is a contact-and-escalation lookup rather than a product or research tool. The verb is only implied ('get' from the name), keeping it just short of 5.

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?

The described content implies its own use cases (finding a branch's contact details, or routing a grievance up the escalation chain), and it notes the city filter is optional. It does not, however, state when to prefer this over the sibling tools or any preconditions, leaving usage to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources