Skip to main content
Glama

SMIFS Limited

Search SMIFS FAQs

search_faq
Read-onlyIdempotent

Keyword search across the SMIFS FAQ page and the FAQs on every product page (accounts, KYC, trading, PMS, mutual funds, charges, compliance, support). Returns matching questions with their answers, category and source URL; with no query, returns the first questions. General information, not personalised advice.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many answers to return (1-20).
queryNoWords to look for, for example "demat account" or "margin trading".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: what is returned (questions with answers, category, source URL) and the fallback behavior when no query is supplied. It stops short of noting result ordering or relevance ranking.

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?

Two dense sentences with no filler; the search scope is front-loaded, the return shape follows, and the disclaimer closes. Every clause carries information an agent can act on.

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 usefully describes the return payload and the empty-query fallback, which is enough to call the tool correctly. Minor gaps remain around result ordering and how limit interacts with relevance, but nothing essential is missing for a two-parameter read tool.

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, but the description adds meaning the schema does not: omitting the query returns the first questions, which tells the agent the parameter is genuinely optional and what happens without it. The limit parameter's effect is left entirely to the schema.

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?

States a specific verb (keyword search) and resource (SMIFS FAQ page plus FAQs on every product page), and enumerates the covered domains (accounts, KYC, trading, PMS, mutual funds, charges, compliance, support). That scope makes it distinguishable from search_research and the get_* lookups without opening any schema.

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 description implies usage through its scope statement and the caveat 'General information, not personalised advice', but it never says when to prefer this over search_research or the get_* info tools. The 'no query' sentence describes behavior rather than a when-to-use rule.

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