Skip to main content
Glama

SMIFS Limited

SMIFS company profile

get_company_profile
Read-onlyIdempotent

Legal identity and regulatory registrations of SMIFS Limited (CIN, SEBI broker, depository participant, research analyst and PMS numbers, AMFI, APMI, IRDAI), exchange and depository memberships, registered office, and official contact emails. Use this to verify the firm or answer "who is SMIFS".

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_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered externally. The description adds the substantive point that the payload is a fixed set of legal/regulatory identifiers, but it says nothing about freshness, sourcing, or completeness of those numbers, which matters for a verification tool.

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 sentences, front-loaded with the resource and its contents, with zero filler. The dense parenthetical registry list is compact but requires slow parsing, which keeps it just short of ideal.

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 parameters, no output schema, and full annotation coverage, the description must carry the return-value burden and largely does by naming the categories of data returned. It stops short of describing the response structure or whether the registrations are current, the only real gaps for a lookup tool of this simplicity.

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?

The tool takes zero parameters and the schema is empty, so there is nothing to disambiguate and the 0-param baseline of 4 applies. The field enumeration in the description usefully signals what comes back rather than adding parameter meaning.

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 enumerates exactly what the tool returns (CIN, SEBI broker/DP/research analyst/PMS numbers, AMFI, APMI, IRDAI, memberships, registered office, contact emails) and frames it as answering "who is SMIFS". That makes the resource unambiguous. It loses a point only because it is framed as a content list rather than a verb, and the "official contact emails" scope blurs slightly against the sibling get_contact_and_grievance.

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?

It gives one clear positive trigger: "Use this to verify the firm or answer 'who is SMIFS'." There is no when-not guidance and no sibling is named, even though get_contact_and_grievance plausibly overlaps on contact details, leaving the agent to guess which to call for emails.

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