Skip to main content
Glama

regulatory-radar

by io.github.jdhart81
OverviewDiscussionsAdmin

monitor_changes

Watch curated regulatory effective dates and deadlines in a bounded window.

`since_days` controls both recently effective dates behind today and
effective/deadline dates ahead of today. This is a source-linked watch
over the curated Viridis dataset, not a live external regulatory feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicsNo
request_idNo
since_daysNo
payment_refNo
jurisdictionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topics
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Topics"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / payment_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Payment Ref"
+}
    • addedInput schema / properties / request_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Request Id"
+}
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses data provenance ('source-linked watch over the curated Viridis dataset, not a live external regulatory feed'), which is real context. It says nothing about auth needs, result shape, pagination, or freshness limits.

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?

Three short sentences with the core scope front-loaded and the provenance caveat last. No filler, though the `since_days` sentence is a bit terse for the parameter's dual behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema removes the need to explain return values, and the provenance note is a genuine addition. But with five parameters at 0% schema coverage and no annotations, the description leaves an agent under-informed about most inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only explains `since_days` (covering both directions of the window). The other four parameters — including the required `jurisdiction`, plus `topics`, `request_id`, and `payment_ref` — are left entirely undocumented.

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?

States a specific verb and resource: 'Watch curated regulatory effective dates and deadlines in a bounded window.' This clearly distinguishes a monitoring/watch operation from a one-shot scan, though it never names the closest sibling (scan_regulations) explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains that `since_days` sets a bounded look-back and look-ahead window, which implies when the tool is useful. However, there is no explicit when-to-use-vs-alternative guidance and no when-not guidance relative to scan_regulations or assess_compliance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All regulatory-radar toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources