Skip to main content
Glama

Indian Cyber Regulation Register (BitScore)

Search the Indian cyber regulation register

search_instruments
Read-onlyIdempotent

Search every cyber and data-protection instrument binding Indian regulated entities (RBI, SEBI, IRDAI, PFRDA, IFSCA, CERT-In, MeitY/DPDP): reference number, issue date, status, who it binds and the deadlines it sets. Filter by free text, issuer or status. Returns summaries; use get_instrument for one entry in full.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results, 1–50. Default 20.
queryNoWords to match against the name, reference number and who it binds, e.g. "outsourcing", "NBFC", "2024/113".
issuerNoOnly instruments from this issuer.
statusNoOnly instruments with this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / issuer / enum
      Previous value: -[
      -  "RBI",
      -  "SEBI",
      -  "IRDAI",
      -  "IFSCA",
      -  "CERT-In",
      -  "MeitY"
      -]New value: +[
      +  "RBI",
      +  "SEBI",
      +  "IRDAI",
      +  "PFRDA",
      +  "IFSCA",
      +  "CERT-In",
      +  "MeitY"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, non-open-world behavior. The description adds useful behavioral context by stating that it returns summaries and that get_instrument should be used for a full entry, though it does not discuss pagination, rate limits, or result ordering beyond the limit parameter.

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?

The description is three sentences, front-loaded with scope and followed by filtering behavior and the full-record alternative. Every sentence adds information without redundancy.

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 read-only search tool with four fully documented parameters and no output schema, the description covers scope, filtering, and the summary-versus-full-record distinction well. It leaves minor gaps around result ordering or pagination behavior beyond what the limit parameter implies.

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 the input schema already documents query, issuer, status, and limit thoroughly. The description only restates that free-text, issuer, and status filters exist, without adding syntax or format guidance beyond 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?

The description uses a specific verb and resource: search cyber and data-protection instruments binding Indian regulated entities. It scopes the register by naming the issuers and the metadata covered, and it distinguishes the tool from get_instrument, which retrieves one entry in full.

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?

It clearly states that results can be filtered by free text, issuer, or status, and explicitly routes users to get_instrument for full detail. However, it does not disambiguate this search from sibling tools such as find_applicable_regulations or find_global_cyber_regulations.

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