Skip to main content
Glama

Leadgen ONRC Romania

lookup_director

Find Romanian companies by director or legal representative name.

Searches the ONRC reprezentanti table (persoana_imputernicita) via a
ranked FTS5 index; diacritic-insensitive ('popescu' matches 'POPESCU').
Returns companies with their director names and roles.

Args:
    name: Director / representative name to search for (e.g. "Ion Popescu").
    max_results: Maximum number of companies to return (1-100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
max_resultsNo

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses that the tool searches a specific table via ranked FTS5 and returns company and director data. It does not mention side effects, but for a read-only search this is acceptable; it is transparent about its core behavior.

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?

The description is concise, using two sentences plus parameter explanations. It includes useful technical details (FTS5, diacritic-insensitive) without being verbose. The use of terms like 'ONRC' and 'FTS5' might be niche, but they are not excessive.

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 states what the tool returns (companies with director names and roles) and the parameter range for max_results. It does not cover error cases, pagination, or what happens with no matches, but for a simple search tool this is reasonably complete.

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

Parameters4/5

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

Schema coverage is 0% with no parameter descriptions, but the description provides meaning for both parameters: name is the director/representative to search for, and max_results is the maximum number of companies returned (1-100). This adds value beyond the schema, though more detail on expected formats or constraints would improve it.

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 finds Romanian companies by director or legal representative name, with a specific verb and resource. It distinguishes itself from sibling tools like lookup_business and lookup_domain by focusing on director-based search.

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?

The description explains the search mechanism (FTS5, diacritic-insensitive) and the target table, giving clear functional context. It does not explicitly mention when to use this vs. alternatives, but the purpose is implied strongly enough for an agent to infer appropriate use.

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