Skip to main content
Glama

Leadgen ONRC Romania

lookup_business

Search the Romanian business registry (official ONRC data) for companies.

Data source: official ONRC open-data snapshot (data.gov.ro), loaded locally.
Name queries use a ranked FTS5 index and are diacritic-insensitive
('paval' matches 'PAVĂL'); digit queries match the CUI exactly, falling
back to a CUI prefix match when the exact code is unknown.

Args:
    query: Company name or CUI (tax ID) to search for.
    max_results: Maximum number of companies to return (1-100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations present, the description carries the burden of disclosing behavior. It mentions the local data source, FTS5 indexing, diacritic-insensitive matching, and CUI exact/prefix fallback, but it does not explicitly state that the operation is read-only or mention any side effects, rate limits, or error behavior.

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?

The description is compact and well-organized, with a clear summary followed by useful matching details and an Args list. There is no redundant or irrelevant content.

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?

The description provides sufficient context for a search operation, covering the data source, matching semantics, and parameter constraints. It does not specify result fields or pagination, but for a simple lookup tool with no output schema these omissions are acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

The Args section in the description fully explains query as a company name or CUI and defines max_results with the allowed range 1-100. It also clarifies the special behavior for digit queries, which goes well beyond the minimal schema information.

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 clearly states the tool's specific action: searching the Romanian business registry for companies using official ONRC data. The verb and resource are explicit, and the tool is easily distinguished from sibling tools like enrich_company or lookup_financials.

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

Usage Guidelines3/5

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

The description explains when to use the tool for company name or CUI lookups and details matching behavior, but it does not explicitly contrast it with alternative sibling tools such as lookup_financials or enrich_company. More direct guidance on when not to use this tool would improve clarity.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources