Skip to main content
Glama

Regulatory Coverage

get_regulatory_coverage
Read-only

What the corpus covers and how fresh each source is. Use it before saying nothing was published. A stale or failing source means our crawl is behind, not that the publisher stopped: say so. A null time means not yet checked, never fine. Free.

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

Input Schema

NameRequiredDescriptionDefault
publisherIdNoPublisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string.
includePausedNoTrue to include sources we have paused.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / includePaused / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / includePaused / default
      Added value: +null
    • changedInput schema / properties / includePaused / description
      Previous value: -"Include sources that are deliberately switched off. Off by default: a paused source's document count will not grow, and listing it beside live ones implies coverage that is not being maintained."New value: +"True to include sources we have paused."
    • removedInput schema / properties / includePaused / type
      Removed value: -"boolean"
    • addedInput schema / properties / publisherId / anyOf
      Added value: +[
      +  {
      +    "items": {
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / publisherId / default
      Added value: +null
    • changedInput schema / properties / publisherId / description
      Previous value: -"Restrict the source list to these publishers. The totals stay corpus wide. Repeatable."New value: +"Publisher ids, e.g. ['sebi', 'rbi']. A list of separate values, never one comma-joined string."
    • removedInput schema / properties / publisherId / items
      Removed value: -{
      -  "maxLength": 64,
      -  "type": "string"
      -}
    • removedInput schema / properties / publisherId / type
      Removed value: -"array"
    • removedInput schema / required
      Removed value: -[]
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful interpretive context that annotations cannot convey: a stale/failing source means the crawl is behind, and a null time means unchecked rather than fine, plus a hint that the call is cheap ("Free"). It does not describe result shape, but an output schema exists to carry that.

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?

Four short sentences, front-loaded with the core purpose and followed by the actionable interpretation rules. Every clause is load-bearing: the staleness framing and the null-means-unchecked rule both prevent concrete agent errors, and nothing is repeated from the schema or annotations.

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 an output schema present, the description does not need to enumerate return fields, and it correctly focuses on purpose, timing, and result interpretation for a two-parameter read tool with no required arguments. The only gap is that it never mentions scoping behavior, i.e. that omitting publisherId covers everything, though the schema's defaults make that inferable.

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 coverage is 100%, including the notable warning that publisherId is a list of separate values rather than a comma-joined string, and the meaning of includePaused. The description adds nothing about either parameter, so it neither compensates for nor improves on what the schema already says; baseline 3 applies.

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?

"What the corpus covers and how fresh each source is" names a specific resource (per-source coverage and freshness) and is clearly distinct from the document/search siblings, which return content rather than corpus metadata. The verb is implicit rather than stated outright, which keeps it from a 5.

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?

"Use it before saying nothing was published" gives an explicit triggering condition tied to a common failure mode, which is exactly the kind of when-to-use guidance an agent needs. It stops short of naming alternatives or stating when not to call it, so no exclusion or sibling routing is provided.

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.