Leadgen ONRC Romania

Stop watching a company or activity

unwatch

DestructiveIdempotent

Stop tracking a company (CUI) or a CAEN code (including its county); the tracking and its reference status will be deleted; free of charge. Pass cui, or code (plus the county it was watched in, if any), on your API key. Unwatching something you do not watch changes nothing (removed: 0). list_watches lists your watches. Not counted as a lookup.

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

Input Schema

Name	Required	Description
`cui`	No	CUI of a watched company (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

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.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / cui / description

Previous value: -"CUI of a watched firm (e.g. '2816464'); give this or code."New value: +"CUI of a watched company (e.g. '2816464'); give this or code."

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.5/5.0

Behavior5/5

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

Beyond annotations, it discloses that the tracking and its reference status will be deleted, that the operation is free of charge, that it is not counted as a lookup, and that unwatching an unwatched item returns removed: 0. These are meaningful behavioral details for a destructive but idempotent tool.

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?

The description is dense and front-loaded: it states what is deleted, how to select the target, the no-op behavior, and billing implications in a few short clauses. Every sentence earns its place.

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?

With annotations covering destructiveness and idempotency, a full schema, and an output schema, the description adds the remaining context an agent needs: cost, lookup accounting, deletion side effects, and no-op behavior.

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%, so the schema already documents cui, code, and county semantics. The description reinforces the choice between cui and code (plus optional county), but does not add syntax or format details beyond what the schema provides.

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?

The description opens with a specific verb+resource: 'Stop tracking a company (CUI) or a CAEN code (including its county)'. This clearly distinguishes the tool from sibling write tools like watch_company and watch_caen.

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?

It tells the agent how to invoke the tool (pass cui, or code plus county) and names list_watches for viewing existing watches. It also clarifies that unwatching an untracked item is a no-op. However, it does not explicitly route to watch_company/watch_caen as the alternative for starting a watch.

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.