Leadgen ONRC Romania

List my watches

list_watches

Read-onlyIdempotent

List every company and CAEN activity your API key watches, each with what changed since the last poll_watchlist, most severe first. A peek: nothing is marked as seen (poll_watchlist does that). Free and never counted as a lookup, also with 0 left today.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`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).
`limits`	No	plan, enforced, max (the plan's watchlist size), used.
`changed`	No	Number of watches with news.
`message`	No	A sentence for the caller.
`watches`	No	Per watch: kind (company or caen), target (CUI or code), county, createdAt, lastSeenAt, name (a company) or since (a code), severity (0 = no change) and change (what changed, or null).
`attribution`	No	The credit line to keep when redistributing the data (CC BY 4.0).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, but the description adds genuinely new operational facts: it is free, never counted as a lookup, and still works with 0 lookups left today, plus that it does not mark items as seen. Quota and side-effect behavior are exactly what an agent cannot infer from structured fields.

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 short sentences, with the core action and result ordering front-loaded, followed by the peek/no-side-effect clarification and the quota note. No filler or repetition of annotation content.

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?

The return shape is covered by the output schema, and the description still adds the ordering and 'what changed since' semantics that the schema alone wouldn't convey. Nothing needed to invoke it correctly is missing.

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; there is nothing for the description to disambiguate. The implicit ordering guarantee ('most severe first') is a useful bonus but not a parameter concern.

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 gives a specific verb and resource ('List every company and CAEN activity your API key watches') plus result shaping ('each with what changed since the last poll_watchlist, most severe first'). It explicitly distinguishes itself from the sibling poll_watchlist, so an agent can choose between them without inspecting schemas.

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

Usage Guidelines5/5

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

It names the alternative (poll_watchlist) and the exact condition that separates them: this is 'A peek: nothing is marked as seen (poll_watchlist does that).' An agent knows to call this when it wants to inspect state without consuming/acknowledging changes.

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.