Skip to main content
Glama

Indian Cyber Regulation Register (BitScore)

Indian cyber incident reporting deadlines

india_incident_reporting_deadlines
Read-onlyIdempotent

Every incident-reporting clock an Indian entity owes — CERT-In six hours, the sectoral regulator (RBI, including non-bank payment system operators, SEBI, IRDAI, PFRDA, IFSCA), SEBI LODR, NCIIPC, DPDP — each with its trigger, recipient, channel and source clause. Give noticed_at to get wall-clock IST due times. Clocks run in parallel; none discharges another.

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": {
      "sector": "<sector>",
      "listed": "<listed>",
      "protected_system": "<protected_system>",
      "personal_data": "<personal_data>"
    },
    "name": "india_incident_reporting_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
listedYesListed on an Indian stock exchange.
sectorYesSectoral regulator, or "none".
ifsca_miiNoIFSC market infrastructure institution (stock exchange, clearing corporation, depository).
pso_smallNoFor sector "rbi-pso": a small non-bank payment operator — a small PPI issuer or Instant Money Transfer Operator. The six-hour RBI report then binds only from 1 April 2028.
rbi_classNoRequired when sector is "rbi".
nbfc_layerNoFor an NBFC: its layer under Scale-Based Regulation.
noticed_atNoOptional. When the incident was noticed or brought to notice, ISO 8601 with offset, e.g. 2026-10-01T14:30:00+05:30.
ifsca_exemptNoIFSCA RE inside either exemption tier of the 2025 Guidelines.
personal_dataYesThe incident involves digital personal data.
pfrda_category_iNoPFRDA Category I NPS intermediary — a CRA or pension fund (adds the 48-hour subscriber-impact report and the quarterly return).
protected_systemYesOperates a notified Protected System (brings NCIIPC).
sebi_broker_or_dpNoSEBI stock broker or depository participant (adds a six-hour leg to the exchanges/depositories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / pso_small
      Added value: +{
      +  "description": "For sector \"rbi-pso\": a small non-bank payment operator — a small PPI issuer or Instant Money Transfer Operator. The six-hour RBI report then binds only from 1 April 2028.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / sector / enum
      Previous value: -[
      -  "rbi",
      -  "sebi",
      -  "irdai",
      -  "pfrda",
      -  "ifsca",
      -  "none"
      -]New value: +[
      +  "rbi",
      +  "rbi-pso",
      +  "sebi",
      +  "irdai",
      +  "pfrda",
      +  "ifsca",
      +  "none"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / pfrda_category_i
      Added value: +{
      +  "description": "PFRDA Category I NPS intermediary — a CRA or pension fund (adds the 48-hour subscriber-impact report and the quarterly return).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / sector / enum
      Previous value: -[
      -  "rbi",
      -  "sebi",
      -  "irdai",
      -  "ifsca",
      -  "none"
      -]New value: +[
      +  "rbi",
      +  "sebi",
      +  "irdai",
      +  "pfrda",
      +  "ifsca",
      +  "none"
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world lookup, so the bar is lower, but the description still adds substantive behavior: outputs carry trigger/recipient/channel/source clause, and the parallel-clock rule is a real semantic warning not present in any structured field. Return shape is described despite there being no output schema. What is missing is edge behavior (e.g. what is returned when sector is 'none' or no clock binds).

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?

Three dense sentences, front-loaded with the covered clocks before the parameter hint and the parallel-clock caveat. The parenthetical regulator list is information-bearing rather than decorative, and there is no filler.

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 12-parameter tool with no output schema, the description covers the domain, the returned fields, and the key interaction between clocks, which is what an agent needs to call it correctly. Minor residual gaps are the absence of any fallback guidance when no clock applies and no note that this is reference information rather than a filing action.

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 baseline is 3; the description earns a point by explaining the consequence of supplying noticed_at (wall-clock IST due times appear only then), which is a meaning-level detail the schema's 'Optional. When the incident was noticed...' does not convey. The regulator list in the description also glosses the sector enum values, though it does not map each enum to a clock.

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 enumerates exactly what the tool covers (CERT-In, RBI incl. PSOs, SEBI/LODR, IRDAI, PFRDA, IFSCA, NCIIPC, DPDP) and what each entry contains (trigger, recipient, channel, source clause), which is far more specific than the title. The action is conveyed elliptically through a noun phrase rather than an explicit verb, and the jurisdictional split from the sibling us_eu_incident_reporting_deadlines is implied by 'an Indian entity owes' rather than stated.

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?

'Give noticed_at to get wall-clock IST due times' tells the agent when that optional parameter changes the output, and 'Clocks run in parallel; none discharges another' pre-empts a common misinterpretation. There is no explicit when-not guidance or named alternative (e.g. the US/EU counterpart) for out-of-scope entities, so it stops short of full routing guidance.

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