e-Factura Validator (Romania)

company_financials

Read-onlyIdempotent

Use when you need a Romanian company's size or financial health from its CUI (credit check before invoicing or selling on terms, lead qualification, due diligence): the annual statement filed with ANAF: CAEN code, turnover, revenue, expenses, net_result (profit positive, loss negative), employees, assets, debts, equity. Without year: the last closed year with a statement. Only companies file statements (not PFA). Free, shares the 100 lookups per day per IP of lookup_company.

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": {
      "cui": "<cui>"
    },
    "name": "company_financials"
  }
}

Input Schema

Name	Required	Description	Default
`cui`	Yes	CUI, with or without RO
`year`	No	Financial year (omit for the last filed one)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses the quota model (free, shared 100 lookups per day per IP with lookup_company), the default year behavior (last closed year with a statement), and a failure mode (PFA entities do not file). These are operational facts an agent cannot get from annotations or schema.

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?

A single dense paragraph front-loaded with 'Use when...', followed by returned fields, default behavior, an entity-type caveat, and quota. No sentence is filler, though the parenthetical field list is long it is all information-bearing.

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?

There is no output schema, and the description compensates by listing the returned metrics and the net_result sign convention, plus the year default and rate-limit sharing. For a 2-parameter read-only lookup, nothing an agent needs to call 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 coverage is 100%, so the schema already documents both parameters including 'omit for the last filed one'. The description confirms the default-year semantics and CUI accepts an optional RO prefix, but adds no new syntax or format detail; 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-less but precise action (fetch annual statement filed with ANAF for a Romanian company identified by CUI) and enumerates the exact returned fields: CAEN code, turnover, revenue, expenses, net_result, employees, assets, debts, equity. It is clearly distinguishable from lookup_company, which is referenced for shared quota rather than identity data.

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 decision contexts: credit check before invoicing or selling on terms, lead qualification, due diligence, plus a limitation that only companies (not PFA) file statements. It does not explicitly route the agent elsewhere for identity/registration data, so the alternative-selection guidance is present but not fully closed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All e-Factura Validator (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.

Resources

Need Help?