Skip to main content
Glama

Indian Cyber Regulation Register (BitScore)

Which Indian cyber regulations apply to an entity

find_applicable_regulations
Read-onlyIdempotent

Given an Indian entity class, whether it is listed and whether it handles personal data, returns the cyber and data-protection instruments that bind it, why each applies, a caution where one is commonly misapplied, and its next dated deadline. RBI classes each map to their own 2026 Directions; RRBs and LABs have none, and the result says so.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_class": "<entity_class>",
      "listed": "<listed>",
      "handles_personal_data": "<handles_personal_data>"
    },
    "name": "find_applicable_regulations"
  }
}

Input Schema

NameRequiredDescriptionDefault
listedYesListed on an Indian stock exchange (brings SEBI LODR disclosure).
entity_classYesThe entity’s class.
handles_personal_dataYesProcesses digital personal data of individuals in India (brings DPDP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / entity_class / enum
      Previous value: -[
      -  "commercial-bank",
      -  "sfb",
      -  "payments-bank",
      -  "ucb",
      -  "aifi",
      -  "nbfc",
      -  "cic",
      -  "rrb",
      -  "lab",
      -  "sebi-re",
      -  "insurer",
      -  "nps-intermediary",
      -  "ifsca-re",
      -  "other"
      -]New value: +[
      +  "commercial-bank",
      +  "sfb",
      +  "payments-bank",
      +  "ucb",
      +  "aifi",
      +  "nbfc",
      +  "cic",
      +  "rrb",
      +  "lab",
      +  "pso",
      +  "pso-small",
      +  "sebi-re",
      +  "insurer",
      +  "nps-intermediary",
      +  "ifsca-re",
      +  "other"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / entity_class / enum
      Previous value: -[
      -  "commercial-bank",
      -  "sfb",
      -  "payments-bank",
      -  "ucb",
      -  "aifi",
      -  "nbfc",
      -  "cic",
      -  "rrb",
      -  "lab",
      -  "sebi-re",
      -  "insurer",
      -  "ifsca-re",
      -  "other"
      -]New value: +[
      +  "commercial-bank",
      +  "sfb",
      +  "payments-bank",
      +  "ucb",
      +  "aifi",
      +  "nbfc",
      +  "cic",
      +  "rrb",
      +  "lab",
      +  "sebi-re",
      +  "insurer",
      +  "nps-intermediary",
      +  "ifsca-re",
      +  "other"
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, and the description adds real substance beyond them: the shape of the answer (each instrument, why it applies, a caution where commonly misapplied, next dated deadline). It also discloses an edge case up front — RRBs and LABs have no instruments and the result says so — which prevents an agent from misreading an empty answer as an error.

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

Conciseness4/5

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

Front-loaded with the input-to-output contract, then the domain caveat. The first sentence is long because it enumerates four return components, but almost every clause carries information and nothing is repetitious.

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 only three fully documented parameters and no output schema, the description carries the burden of describing returns, and it does so at the level of content (instruments, rationale, caution, deadline). It stops short of describing the structure of an entry or ordering of results, which is a minor residual gap for a lookup 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; the description adds meaning by tying entity_class to downstream behavior (each RBI class maps to its own 2026 Directions, while rrb and lab map to none). It does not add syntax or format detail beyond the enum and boolean descriptions, so it sits just above baseline rather than at the top.

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 ('returns') and resource ('the cyber and data-protection instruments that bind it') with fully specified inputs. Scope is narrowed to Indian entities, which implicitly separates it from find_global_cyber_regulations, and the response content (applicability rationale, misapplication caution, next dated deadline) is spelled out so an agent knows what it gets.

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?

Usage context is clear: provide entity class, listing status and personal-data handling to get binding instruments. It also gives a domain rule of thumb (RBI classes each map to their own 2026 Directions; RRBs and LABs have none). It does not explicitly name when to prefer a sibling such as find_global_cyber_regulations, so there is no explicit exclusion.

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