Leadgen ONRC Romania

Annual financial statements

lookup_financials

Read-onlyIdempotent

Annual financial statements for a Romanian company from Ministry of Finance filings, every fiscal year on record since 2008: revenue, profit, headcount and balance-sheet lines in RON with each year's ratios (growth, margins, equity ratio, liquidity), plus a summary (3/5/10-year CAGR, loss years, health score). Resolve the company with lookup_business first if you only have a name.

Input Schema

Name	Required	Description	Default
`cui`	Yes	Romanian tax identification number (CUI), e.g. '2816464'; 'RO' and leading zeros are accepted.

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.
`found`	No	Whether any filing is on record.
`total`	No	Number of fiscal years returned.
`years`	No	Per fiscal year: revenue, profit, loss, netResult, employees, assets, debt, equity (RON) and that year's ratios.
`source`	No	Data source: onrc (registry) or mfp (Ministry of Finance filings).
`message`	No	A sentence for the caller.
`summary`	No	History, revenue growth (3/5/10-year CAGR), latest ratios, health score and band, flags.
`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 29, 2026

changedOutput schema / description

Previous value: -"Every annual filing on record for the firm, newest first (RON)."New value: +"Every annual filing on record for the company, newest first (RON)."

changedOutput schema / properties / cui / description

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

Changed2 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."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Every annual filing on record for the firm, newest first (RON).",
+  "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"
+      ]
+    },
+    "attribution": {
+      "description": "The credit line to keep when redistributing the data (CC BY 4.0).",
+      "type": [
+        "string",
+        "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"
+      ]
+    },
+    "found": {
+      "description": "Whether any filing is on record.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A sentence for the caller.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "description": "Data source: onrc (registry) or mfp (Ministry of Finance filings).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "History, revenue growth (3/5/10-year CAGR), latest ratios, health score and band, flags.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Number of fiscal years returned.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "years": {
+      "description": "Per fiscal year: revenue, profit, loss, netResult, employees, assets, debt, equity (RON) and that year's ratios.",
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real value beyond them: historical depth (since 2008), currency (RON), which line items and derived ratios are included, and the summary block with CAGR/loss years/health score. No mention of failures for unknown CUIs or of rate/pagination behavior, which keeps it below 5.

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?

Two sentences, zero filler: the first front-loads the data payload, the second front-loads the prerequisite. The dense parenthetical lists are informative rather than redundant, and the operational instruction comes last where it is easy to act on.

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 not be explained, and the annotation set covers the safety profile; the description supplies scope, source, currency, and the prerequisite lookup. Missing only edge-case behavior for a company with no filings or an invalid CUI.

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?

Only one parameter and the schema already documents it at 100% coverage, including the 'RO' prefix and leading-zero tolerance. The description adds no further CUI semantics (e.g., where to find it, what happens if it is stale), so the 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 and resource ('Annual financial statements for a Romanian company') plus the exact source (Ministry of Finance filings) and scope (every fiscal year since 2008). It enumerates the returned content classes (revenue, profit, headcount, balance-sheet lines, ratios, summary), so an agent can tell this apart from lookup_financial_ratios or lookup_business without opening a 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?

Gives an explicit prerequisite: 'Resolve the company with lookup_business first if you only have a name,' which tells the agent the CUI is a hard requirement and how to obtain it. It does not contrast with the nearby lookup_financial_ratios sibling, so when-to-use vs that alternative is left implicit.

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.