Leadgen ONRC Romania

Company profile with website contacts

enrich_company

Read-onlyIdempotent

A whole-firm profile in one call: the ONRC registry record plus the contacts discovered on that company's website, each labelled with a confidence and a source. Prefer this over lookup_business followed by extract_contacts when you want everything about one company. cui is its tax code; website overrides the registered one; max_pages bounds the crawl; refresh=true crawls now instead of answering from the cache.

Input Schema

Name	Required	Description
`cui`	Yes	Romanian tax identification number (CUI), e.g. '2816464'; 'RO' and leading zeros are accepted.
`refresh`	No	true crawls now even if a cached result exists (default false: answer from the cache when there is one).
`website`	No	Optional website override (domain or URL). When omitted, the company's registered website is used (an error if none is on file).
`max_pages`	No	Maximum number of pages to crawl (1-20, default 5).

Output Schema

Name	Required	Description
`cui`	No	The company's CUI.
`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.
`company`	No	A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address (a sole trader's PFA/II/IF locality only in an answer listing several companies, with addressScope: locality), county, city, website, phone as declared (+ phoneSource: ANAF, declared by the taxpayer; phoneStatus: valid, corrected with phoneSuggestion, or unverified: check before calling), caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the company's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url).
`crawled`	No	true when the site was crawled for this answer.
`message`	No	A sentence for the caller.
`website`	No	The website crawled.
`cacheHit`	No	true when answered from the cache.
`contacts`	No	Contacts found, each with type, value, confidence and source; an email also has personal (true for a firstname.lastname@ address: GDPR art. 14 and Law 506/2004 apply), role addresses first.
`crawlError`	No	Why the crawl failed, if it did.
`pagesCrawled`	No	Pages read.
`websiteSource`	No	Where the website came from: registry or override.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 29, 2026

changedInput schema / properties / website / description

Previous value: -"Optional website override (domain or URL). When omitted, the firm's registered website is used (an error if none is on file)."New value: +"Optional website override (domain or URL). When omitted, the company's registered website is used (an error if none is on file)."

changedOutput schema / description

Previous value: -"The firm's registry record plus the contacts found on its website."New value: +"The company's registry record plus the contacts found on its website."

changedOutput schema / properties / company / description

Previous value: -"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address (a sole trader's PFA/II/IF locality only in an answer listing several firms, with addressScope: locality), county, city, website, phone (+ phoneSource: ANAF, declared by the taxpayer), caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."New value: +"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address (a sole trader's PFA/II/IF locality only in an answer listing several companies, with addressScope: locality), county, city, website, phone as declared (+ phoneSource: ANAF, declared by the taxpayer; phoneStatus: valid, corrected with phoneSuggestion, or unverified: check before calling), caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the company's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."

changedOutput schema / properties / cui / description

Previous value: -"The firm's CUI."New value: +"The company's CUI."

Changed2 schema fields changedOct 19, 2026

changedOutput schema / properties / company / description

Previous value: -"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."New value: +"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address (a sole trader's PFA/II/IF locality only in an answer listing several firms, with addressScope: locality), county, city, website, phone (+ phoneSource: ANAF, declared by the taxpayer), caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."

changedOutput schema / properties / contacts / description

Previous value: -"Contacts found, each with type, value, confidence and source."New value: +"Contacts found, each with type, value, confidence and source; an email also has personal (true for a firstname.lastname@ address: GDPR art. 14 and Law 506/2004 apply), role addresses first."

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / company / description

Previous value: -"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity}], directors, status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."New value: +"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity (RO), activityEn}], directors, representatives [{name, role}], status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / company / description

Previous value: -"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity}], directors, status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, and score/match on name searches. With fields or compact, only the requested keys."New value: +"A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity}], directors, status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, url (the firm's public record page to share with the user; null for sole traders and other natural persons), and score/match on name searches. With fields or compact, only the requested keys (compact keeps url)."

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / cui / description

Added value: +"Romanian tax identification number (CUI), e.g. '2816464'; 'RO' and leading zeros are accepted."

addedInput schema / properties / max_pages / description

Added value: +"Maximum number of pages to crawl (1-20, default 5)."

addedInput schema / properties / refresh / description

Added value: +"true crawls now even if a cached result exists (default false: answer from the cache when there is one)."

addedInput schema / properties / website / description

Added value: +"Optional website override (domain or URL). When omitted, the firm's registered website is used (an error if none is on file)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The firm's registry record plus the contacts found on its website.",
+  "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"
+      ]
+    },
+    "cacheHit": {
+      "description": "true when answered from the cache.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "company": {
+      "additionalProperties": true,
+      "description": "A company record: companyName, cui, registrationCode, registrationDate (DD/MM/YYYY), legalForm, euid, address, county, city, website, phone, caenActivities [{code, activity}], directors, status [{code, name}], latestFinancials {year, revenue, netResult, employees; RON}, anaf {mainCaen, vatPayer, eFactura, inactive}, risk {level, label, reasons, isLead}, source, asOf, and score/match on name searches. With fields or compact, only the requested keys.",
+      "type": "object"
+    },
+    "contacts": {
+      "description": "Contacts found, each with type, value, confidence and source.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "crawlError": {
+      "description": "Why the crawl failed, if it did.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "crawled": {
+      "description": "true when the site was crawled for this answer.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "cui": {
+      "description": "The firm's CUI.",
+      "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"
+      ]
+    },
+    "pagesCrawled": {
+      "description": "Pages read.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "website": {
+      "description": "The website crawled.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "websiteSource": {
+      "description": "Where the website came from: registry or override.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / refresh

Added value: +{
+  "default": false,
+  "title": "Refresh",
+  "type": "boolean"
+}

First observedSep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-redundant behavior: results are cache-backed unless refresh=true forces a crawl, website overrides the registered site, and discovered contacts carry confidence and source labels. Missing only operational details like auth or rate limits.

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 tight sentences: capability first, routing/alternative second, parameter glosses last. Every clause carries information and the most decision-relevant content is front-loaded.

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 and the description still sketches the return shape (registry record + labelled contacts), and schema coverage is full, so nothing an agent needs 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters in detail. The description's parameter notes (cui=tax code, website override, max_pages bounds crawl, refresh bypasses cache) largely restate the schema rather than enriching it. Baseline 3 is appropriate.

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 concrete verb (profile/enrich) and resource (one company), enumerating the two data sources combined: ONRC registry record plus website contacts. This is clearly distinguishable from lookup_business and extract_contacts, which the description names explicitly.

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?

Explicitly says 'Prefer this over lookup_business followed by extract_contacts when you want everything about one company,' giving the agent a concrete decision rule and naming the alternatives. No inference required.

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.

Company profile with website contacts

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources