Leadgen ONRC Romania

Stop watching a company or activity

unwatch

DestructiveIdempotent

Stop watching a company (cui) or a CAEN activity code (code, plus the county it was watched in, if any), on your API key: the watch and its baseline are removed. Unwatching something you do not watch changes nothing (removed: 0). poll_watchlist lists your active watches.

Input Schema

TableJSON Schema

Name	Required	Description
`cui`	No	CUI of a watched firm (e.g. '2816464'); give this or code.
`code`	No	A watched CAEN activity code (e.g. '6210'); give this or cui.
`county`	No	With code: the county the code was watched in (diacritic-insensitive); omit for a nationwide watch.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	true when the request was valid.
`asOf`	No	What to cite: registry (ONRC snapshot date), financialYear (fiscal year of the figures), anaf (day of the ANAF data), snapshot, published, source.
`kind`	No	company or caen.
`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).
`active`	No	The watches you still hold (as in poll_watchlist).
`county`	No	The CAEN watch's county; null for nationwide or a company.
`target`	No	The CUI or CAEN code.
`message`	No	A sentence for the caller.
`removed`	No	1 when the watch was removed, 0 when you did not hold it.
`attribution`	No	The credit line to keep when redistributing the data (CC BY 4.0).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

addedOutput schema / properties / asOf

Added value: +{
+  "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"
+  ]
+}

addedOutput schema / properties / attribution

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

AddedOct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, but the description adds concrete value: it says the watch AND its baseline are removed, that the operation is scoped to 'your API key', and that a redundant call returns 'removed: 0'. That corroborates and enriches the idempotent/destructive annotations rather than merely repeating them.

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 compact sentences, front-loaded with the action and its scope, followed by the no-op guarantee and the cross-reference. Every sentence earns its place.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile; the description supplies the baseline-removal effect, API-key scoping, and the sibling pointer. Only minor gaps (e.g. required-permission context) remain.

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 description coverage is 100%, and each parameter already documents its own meaning, so the baseline is 3. The description restates the cui/code alternation and adds that county is 'the county it was watched in, if any', but contributes no syntax or format detail beyond the schema.

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 (stop watching) and the two interchangeable resource modes (company cui, CAEN code), and distinguishes itself from the watch_company/watch_caen siblings. An agent can identify the inverse operation without opening any 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?

Explains the no-op case ('unwatching something you do not watch changes nothing') and routes the agent to poll_watchlist to see active watches. It lacks an explicit statement of prerequisites or when not to use it, but the context is clear.

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.