Skip to main content
Glama

Romania company

run_ro_companies
Read-onlyIdempotent

Get one company from the Romania registry data (Ministry of Finance / ONRC) by CUI (CIF): name, status and registration date, address, trade register number, authorization act, phone/fax, tax registrations (profit tax, VAT, social contributions, ...) and the latest filed financial indicators (assets, debts, equity, turnover, profit, employees). 15 points per returned record.

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": {
      "company": "<company>"
    },
    "name": "run_ro_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCUI (CIF). e.g. 2816464

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context by listing the returned fields and disclosing that each returned record costs 15 points, which is value beyond the annotations.

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 front-loaded with the core action and identifier, then efficiently lists the returned field groups and point cost. The long field enumeration is purposeful because there is no output schema.

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?

For a one-parameter lookup with no output schema, the description is nearly complete: it identifies the source, the lookup key, and the returned data categories. It does not describe not-found or error behavior, but otherwise gives an agent enough to call the tool correctly.

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%, and the single parameter is already documented as the company CUI/CIF with an example. The description restates that the lookup is by CUI but adds no syntax or format guidance beyond the schema, so 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?

The description states a specific verb and resource: get one Romanian company by CUI (CIF). It enumerates the returned data fields and names the source registry, which distinguishes it from the sibling search tool by making it a single-record lookup keyed by company identifier.

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 usage context is clear: call this when you already have a company CUI and need the full record for that single company. It does not explicitly name run_ro_companies_search as the alternative for name-based discovery, but the identifier-driven scope is sufficiently clear.

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