Skip to main content
Glama

Indian Cyber Regulation Register (BitScore)

India Cyber Threat Scorecard

india_threat_scorecard
Read-onlyIdempotent

Aggregate counts of publicly observed cyber threat activity affecting Indian organisations, by industry vertical and category, for one edition (latest by default). Aggregate only: no organisation is named. A vertical the source did not cover is unmeasured, not zero.

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

Input Schema

NameRequiredDescriptionDefault
editionNoEdition slug, YYYY-MM. Omit for the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / edition / enum
      Previous value: -[
      -  "2026-09",
      -  "2026-08"
      -]New value: +[
      +  "2026-10",
      +  "2026-09",
      +  "2026-08"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / edition / enum
      Previous value: -[
      -  "2026-08"
      -]New value: +[
      +  "2026-09",
      +  "2026-08"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious semantics beyond that: it is aggregate-only with no named organisations, and a missing vertical means 'unmeasured, not zero' — a caveat that directly prevents misinterpreting zero/null values. It does not describe the shape of the returned counts, which is a minor gap.

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 short sentences with zero filler; the scope and breakdown dimensions come first, followed by the two critical interpretive constraints. Every sentence earns its place by either defining scope or preventing a specific misreading.

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 carries the burden of explaining what comes back, and it does reasonably well by stating the counts are grouped by vertical and category for one edition. It stops short of describing field names or whether counts are nested objects, which leaves a small gap for an agent planning to consume the result.

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?

The single parameter is fully documented in the schema (100% coverage) including the YYYY-MM enum values and the 'omit for latest' default. The description's 'for one edition (latest by default)' merely restates the schema, adding no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific resource and scope: aggregate counts of publicly observed cyber threat activity affecting Indian organisations, broken down by industry vertical and category, for a single edition. This is clearly distinct from the deadline-oriented siblings (india_incident_reporting_deadlines, us_eu_incident_reporting_deadlines) and the regulatory-category sibling (sebi_cscrf_category). An agent can tell from the first clause whether this is the right tool.

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 gives clear context for use ('one edition, latest by default') and an implicit exclusion via 'Aggregate only: no organisation is named', which tells the agent this is not the tool for entity-level detail. However, it never names an alternative tool to use when per-organisation data is required, so the routing guidance stops short of explicit alternatives.

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