Skip to main content
Glama

SMIFS Limited

How to open a SMIFS account

get_account_opening_info
Read-onlyIdempotent

Where and how to open a SMIFS demat and trading account, the client login links (macONE), and where to find the investor charter and guide videos. Returns links only; it never starts an application.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured fields. The description adds value beyond that by stating 'Returns links only; it never starts an application,' which tells the agent the output shape (links) and rules out any side effect such as initiating onboarding. It does not describe link formatting or whether links may expire, but that is a minor residual gap.

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?

It is a single front-loaded sentence that enumerates the resource categories first and closes with the most decision-relevant constraint ('Returns links only; it never starts an application'). No filler, no restatement of the title, and every clause carries information.

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?

This is a low-complexity, zero-parameter read tool with no output schema, so the description's burden is modest. It covers scope and return type ('links only') and rules out action-taking. A slight gap remains: it does not say what the returned links point to structurally (e.g., a set of categorized URLs), which matters only mildly given there is no output schema.

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 an empty object, so there is no parameter meaning to convey. Per the baseline for 0-param tools, this dimension is not a differentiator. Nothing in the description misleads about inputs.

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 names a specific resource set: how/where to open a SMIFS demat and trading account, the macONE client login links, the investor charter, and guide videos. That is concrete enough for an agent to know it is an informational lookup rather than an action. It stops short of explicitly distinguishing itself from siblings like get_contact_and_grievance or get_product, so it lands at 4 rather than 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?

Usage is implied by the content enumerated (account opening, login links, charter, videos), so an agent can infer this is the go-to tool for onboarding/first-steps questions. There is no explicit when-to-use statement and no named alternative for adjacent needs such as grievances or product questions. The 'never starts an application' clause clarifies a boundary but is about behavior, not tool selection.

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