Leadgen ONRC Romania

Report missing or wrong data

report_issue

Report to the person who runs Leadgen what is missing or wrong: a missing field, company or source (kind 'gap'), a wrong company record ('wrong_record', pass its cui), a bug, an idea. Free, never counted as a lookup. contact is optional (an address for a reply); nothing is mailed to it automatically. Registry records are corrected at the source (ONRC) and arrive with the next snapshot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>"
    },
    "name": "report_issue"
  }
}

Input Schema

Name	Required	Description	Default
`cui`	No	Optional CUI of the company the report is about (for 'wrong_record').
`kind`	No	One of 'gap' (a missing field, company or source; the default), 'wrong_record' (pass its cui), 'bug', 'idea', 'other'.	gap
`contact`	No	Optional email address for a reply; nothing is mailed to it automatically.
`message`	Yes	The report, in plain words: what is missing or wrong.

Output Schema

Name	Required	Description
`id`	No	The report's id.
`kind`	No	The kind filed.
`note`	No	For wrong_record: how registry records get corrected.
`error`	No	Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
`status`	No	received.
`message`	No	A sentence for the caller.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / cui / description

Previous value: -"Optional CUI of the firm the report is about (for 'wrong_record')."New value: +"Optional CUI of the company the report is about (for 'wrong_record')."

changedInput schema / properties / kind / description

Previous value: -"One of 'gap' (a missing field, firm or source; the default), 'wrong_record' (pass its cui), 'bug', 'idea', 'other'."New value: +"One of 'gap' (a missing field, company or source; the default), 'wrong_record' (pass its cui), 'bug', 'idea', 'other'."

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / contact / description

Added value: +"Optional email address for a reply; nothing is mailed to it automatically."

addedInput schema / properties / cui / description

Added value: +"Optional CUI of the firm the report is about (for 'wrong_record')."

addedInput schema / properties / kind / description

Added value: +"One of 'gap' (a missing field, firm or source; the default), 'wrong_record' (pass its cui), 'bug', 'idea', 'other'."

addedInput schema / properties / message / description

Added value: +"The report, in plain words: what is missing or wrong."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The receipt for the report.",
+  "properties": {
+    "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"
+      ]
+    },
+    "id": {
+      "description": "The report's id.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "kind": {
+      "description": "The kind filed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A sentence for the caller.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "For wrong_record: how registry records get corrected.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "received.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 17, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: it is free and never counted as a lookup, the contact address is not auto-mailed, and registry corrections are fixed at ONRC and only appear in the next snapshot. That turnaround/side-effect information is exactly what an agent needs and cannot infer from readOnlyHint=false.

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?

One front-loaded paragraph that leads with the action and then enumerates kinds and caveats. Dense but every clause carries information; only slight cost is that it packs several ideas into a single sentence.

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 an output schema present, return values need not be explained; the description covers purpose, categorization, cost, and delivery timing. An agent has everything required to call the tool correctly.

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%, so cui, kind, contact and message are already documented. The description largely restates those semantics ('pass its cui', contact not auto-mailed) rather than adding new format or constraint detail, so baseline 3 applies.

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 (report) plus the exact resource and recipient (missing/wrong data to the person who runs Leadgen), and enumerates the report kinds. This cleanly separates it from the surrounding lookup/enrichment siblings, which are read tools.

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?

Gives concrete triggers: missing field, company or source as 'gap', a wrong company record with its cui, a bug, an idea. It doesn't name an alternative sibling or give explicit when-not conditions, but the sibling set is entirely lookups so the contrast is implicitly 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.