Skip to main content
Glama

SMIFS Limited

Investor charter, policies and forms

list_policies_downloads
Read-onlyIdempotent

Investor-protection resources and downloadable documents: investor charter, rights and obligations, policies and guidelines, guidance notes, grievance redressal, KMP and bank details, plus account opening forms, declarations, PMS and MTF documents and client apps, each with its link. Optionally filter by a word in the title.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOnly return items whose title contains this text, for example "nomination" or "PMS".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral detail beyond that: results are items each with an associated link, which signals return shape and that no content bodies are fetched. It does not mention empty-result behavior for an unmatched query, though that is a minor omission for a read-only catalog.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the filter option are front-loaded, but the middle is a long comma-chained catalog of document types that reads as keyword stuffing. That enumeration helps retrieval matching, yet the single 40-plus-word sentence reduces scannability and could be split or trimmed without losing meaning.

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?

For a one-optional-parameter, read-only list tool with full annotation coverage and no output schema, the description supplies what is needed: what is returned (documents with links) and how to narrow it. No output schema exists, so the brief return-value hint is adequate; only the overlap with topically similar siblings remains unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents query as a title-substring filter with the examples "nomination" and "PMS." The description's phrase "filter by a word in the title" restates the schema at roughly the same level of detail rather than adding matching semantics (case sensitivity, substring vs whole-word). Baseline 3 applies when the schema does the work.

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 concrete resource set and enumerates its contents (investor charter, policies, grievance redressal, KMP/bank details, account opening forms, PMS/MTF documents, client apps) and states each comes with a link. An agent can tell this is a document/resource catalog rather than a search or profile tool. It stops short of explicitly distinguishing itself from siblings that overlap in topic, notably get_contact_and_grievance and get_account_opening_info.

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?

The only guidance is "Optionally filter by a word in the title," which is a parameter note rather than a when-to-use rule. Nothing says when to pick this over get_account_opening_info (account opening forms) or get_contact_and_grievance (grievance redressal), both of which are topically covered here. Usage must be inferred from the subject matter alone.

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