Leadgen ONRC Romania

Collect watchlist changes

poll_watchlist

Collect everything the watch tools have found: call it to drain the changeset for every watch owned by your API key, most severe first. Company watches return an 'updated' entry with the changed fields and risk; CAEN and county watches return the 'new' companies registered since the last poll (200 a poll, the rest next).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	No	true when the poll ran.
`asOf`	No	What to cite: registry (ONRC snapshot date), financialYear (fiscal year of the figures), anaf (day of the ANAF data), snapshot, published, source.
`error`	No	Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
`owner`	No	Whose watches these are (key prefix or IP).
`total`	No	Number of watches with news.
`active`	No	Every watch you hold, changed or not: kind (company or caen), target (CUI or code), county, since, name. Remove one with unwatch.
`message`	No	A sentence for the caller.
`watches`	No	Per watch: an 'updated' company with its changed fields and risk, or the 'new' companies registered in a watched activity.
`attribution`	No	The credit line to keep when redistributing the data (CC BY 4.0).
`email_alerts`	No	How to get the same changes by email.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / watches / description

Previous value: -"Per watch: an 'updated' company with its changed fields and risk, or the 'new' firms registered in a watched activity."New value: +"Per watch: an 'updated' company with its changed fields and risk, or the 'new' companies registered in a watched activity."

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties / active

Added value: +{
+  "description": "Every watch you hold, changed or not: kind (company or caen), target (CUI or code), county, since, name. Remove one with unwatch.",
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / attribution

Added value: +{
+  "description": "The credit line to keep when redistributing the data (CC BY 4.0).",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "What changed for your watches since the last poll, most severe first.",
+  "properties": {
+    "asOf": {
+      "description": "What to cite: registry (ONRC snapshot date), financialYear (fiscal year of the figures), anaf (day of the ANAF data), snapshot, published, source.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "email_alerts": {
+      "description": "How to get the same changes by email.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A sentence for the caller.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ok": {
+      "description": "true when the poll ran.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "owner": {
+      "description": "Whose watches these are (key prefix or IP).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Number of watches with news.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "watches": {
+      "description": "Per watch: an 'updated' company with its changed fields and risk, or the 'new' firms registered in a watched activity.",
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations mark this non-readOnly and non-idempotent; the word 'drain' explains why — the changeset is consumed, so a second call returns different results. It further discloses ordering (most severe first) and pagination behavior (200 per poll, remainder next poll), which annotations alone cannot convey. Minor gap: no mention of what happens to undrained changes (expiry, retention).

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?

Two sentences, front-loaded with the action, then the per-watch-type return shapes. Dense and largely waste-free, though the second sentence packs several distinct facts (two return shapes plus pagination) into one clause chain.

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

Completeness5/5

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

Output schema exists, so return values needn't be spelled out, yet the description still gives the shape per watch type and the severity ordering, plus the pagination contract. For a zero-param polling tool this covers everything an agent needs to call it correctly and interpret the result.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly adds no parameter narrative. It does usefully explain the implicit 'cursor' semantics of the poll cycle, which is the only control surface an agent has.

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?

States a specific verb ('drain the changeset') and resource ('every watch owned by your API key'), and scopes it to outputs of the watch* tools, which separates it from list_watches (definitions) and unwatch (removal). An agent can distinguish it from siblings without opening a schema.

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?

'call it to drain the changeset' plus 'since the last poll' makes the polling-cycle usage clear, and the 200-a-poll note implies the caller should re-poll rather than expect everything at once. It stops short of naming list_watches as the alternative for inspecting watch definitions or stating explicit exclusions.

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

All Leadgen ONRC Romania tools Inspect

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.