Skip to main content
Glama

Search Indian Regulatory Documents

search_regulatory_documents
Read-only

Search Indian regulatory publications: circulars, orders, notices and press releases from named government regulators. Not case law, statute text or commentary. Capture began 2026-08-23, so an empty result for an earlier date does not mean nothing was published. Not an in-force view. Filters are lists. Pass nextCursor back unchanged while hasMore is true. total null means not measured; 0 means none. Cost: 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords to search for. Omit to list by filters alone.
idNoFetch these document ids in one call, instead of searching.
sortNoOrder of results. Omit for the default.
limitNoPage size, 1 to 100. Omit to use the default.
cursorNoOpaque. Pass back exactly the nextCursor of the previous page. Do not parse, edit or construct one.
facetsNoTrue to also return the filter values available.
docTypeNoDocument types as returned in results. A list of separate values.
sourceIdNoSource ids (a publisher's sub-sources, as get_regulatory_coverage lists them). A list of separate values, never comma-joined.
publishedToNoISO date, YYYY-MM-DD, as the publisher dated it.
publisherIdNoPublisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string.
publishedFromNoISO date, YYYY-MM-DD, as the publisher dated it.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

With readOnlyHint=true, destructiveHint=false and openWorldHint=false already declared, the safety profile is covered. The description nonetheless adds real behavioral context beyond annotations: coverage start date, the empty-result caveat, the 'not an in-force view' disclaimer, the pagination contract (nextCursor unchanged while hasMore), total null-vs-0 semantics, and a 1-credit cost. It does not describe result ranking or what fields a hit contains, though an output schema exists.

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?

Telegraphic and front-loaded: purpose first, then scope exclusions, then operational caveats, then pagination and cost. Every sentence carries distinct information and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter search tool with a full output schema, this covers everything an agent needs to call it correctly and interpret empty results, plus cost and paging behavior. Return-value shape is delegated to the output schema, which is appropriate.

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 description coverage is 100%, so every parameter is already documented, including the list semantics of publisherId/sourceId and the cursor handling. The description's 'Filters are lists' and 'Pass nextCursor back unchanged while hasMore is true' largely restate the schema rather than adding new meaning, so baseline 3 applies.

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 (search) and a precisely bounded resource: 'Indian regulatory publications: circulars, orders, notices and press releases from named government regulators'. The negative scope ('Not case law, statute text or commentary') sharpens the boundary so an agent can distinguish it from the single-document sibling and from any case-law source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear when-to-use context plus two important exclusions: it is 'Not an in-force view' and capture began 2026-08-23, so a pre-cutoff empty result is not evidence of absence. It stops short of naming which sibling to use for a single known document or for coverage questions, so routing is only partially guided.

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.