viridis-agent-fleet

Overview Schema Source Related Servers Discussions Admin

regulatory-radar__monitor_changes

[regulatory-radar — CSRD/TNFD compliance-as-a-service] Watch curated regulatory effective dates and deadlines in a bounded window.

Instructions

[regulatory-radar — CSRD/TNFD compliance-as-a-service] 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

Name	Required	Description	Default
`topics`	No
`request_id`	No
`since_days`	No
`payment_ref`	No
`jurisdiction`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.13Sep 13, 2026

addedInput schema / properties / request_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Request Id"
+}

addedInput schema / properties / topics

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Topics"
+}

Changed7 schema fields changedv0.1.11Jul 18, 2026
- addedInput schema / properties / jurisdiction / title
```
Added value: +"Jurisdiction"
```
- addedInput schema / properties / payment_ref / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / payment_ref / default
```
Added value: +null
```
- addedInput schema / properties / payment_ref / title
```
Added value: +"Payment Ref"
```
- removedInput schema / properties / payment_ref / type
```
Removed value: -"string"
```
- addedInput schema / properties / since_days / title
```
Added value: +"Since Days"
```
- addedInput schema / title
```
Added value: +"monitor_changesArguments"
```
Changed4 schema fields changedv0.1.9Jul 16, 2026
- removedInput schema / properties / jurisdiction / title
```
Removed value: -"Jurisdiction"
```
- addedInput schema / properties / payment_ref
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / since_days / title
```
Removed value: -"Since Days"
```
- removedInput schema / title
```
Removed value: -"monitor_changesArguments"
```
Changed3 schema fields changedJul 13, 2026
- addedInput schema / properties / jurisdiction / title
```
Added value: +"Jurisdiction"
```
- addedInput schema / properties / since_days / title
```
Added value: +"Since Days"
```
- addedInput schema / title
```
Added value: +"monitor_changesArguments"
```
Changed3 schema fields changedJul 13, 2026
- removedInput schema / properties / jurisdiction / title
```
Removed value: -"Jurisdiction"
```
- removedInput schema / properties / since_days / title
```
Removed value: -"Since Days"
```
- removedInput schema / title
```
Removed value: -"monitor_changesArguments"
```
First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries full burden, and it does disclose two genuinely useful traits: since_days is bidirectional (past effective dates and future deadlines) and the source is a curated static dataset rather than a live feed. However, it says nothing about permissions, payment (the payment_ref param hints at a paywall), rate limits, or return shape.

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 tight sentences with the behavioral constraint (bounded window, curated source) front-loaded; the bracketed product tag is slight overhead but sets domain context. Every sentence carries information.

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

Completeness2/5

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

For a 5-parameter tool with no annotations and no output schema, the definition leaves too much unstated: what a 'watch' response contains, what jurisdiction values are acceptable, what topics filter, and why payment_ref exists. The dual-window behavior explanation is helpful but insufficient.

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% across 5 parameters, and the description only clarifies one of them (since_days), partly duplicating the schema's default. The required jurisdiction parameter, plus topics, request_id, and payment_ref, receive no explanation anywhere, so the description does not compensate for the coverage gap.

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 ('Watch') and a precise resource ('curated regulatory effective dates and deadlines in a bounded window'), with domain framing (CSRD/TNFD). It does not name sibling tools like scan_regulations or assess_compliance, so the agent must infer the boundary between this and the other regulatory-radar tools, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

The description implies usage (monitoring near-term effective dates and deadlines) but never states when to choose this over scan_regulations/assess_compliance/build_evidence_pack, nor any prerequisites. No exclusions or alternative routing are given.

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

Deploy Server

regulatory-radar__monitor_changes

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools