Skip to main content
Glama

What changed in the registry for a company

company_history
Read-onlyIdempotent

Whether the registry record of one company changed between consecutive official ONRC snapshots, and when: one event per snapshot in which anything on the record moved (status, name, legal form, address, registration number). It reports that the record changed, not which field — for the field detail, compare two lookups. Empty for a company that has not changed since the ledger started.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cuiYesRomanian tax identification number (CUI), e.g. '2816464'; 'RO' and leading zeros are accepted.
limitNoHow many recent events to return (1-100).

Output Schema

NameRequiredDescriptionDefault
cuiNoThe CUI that was asked about.
asOfNoledgerStarted and lastRecorded.
noteNoPresent when there is nothing recorded.
countNoHow many events are in this answer.
errorNoSet only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
sourceNoWhere the events come from.
changesNoEvents, newest first: day, field, old, new.
messageNoA sentence for the caller.
snapshotsNoThe snapshots the ledger holds: day, firms, events.

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: event granularity is per-snapshot, it reports that a change occurred but not which field, and an empty result means no change since the ledger started.

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?

Three sentences, front-loaded with the core behavior, then the key limitation (no field detail), then the empty-result semantics. No filler; each sentence carries distinct information.

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-value structure needn't be explained, and the description covers the important semantic edge cases (granularity, empty result, no field detail). Minor gap: it doesn't mention how the limit interacts with the event list, though the schema documents that parameter.

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 description coverage is 100%, with both cui and limit fully documented in the schema, so the baseline is 3. The description adds no syntax or format detail about the parameters beyond what the schema already provides.

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: reports whether a company's ONRC registry record changed between consecutive snapshots, with one event per snapshot. It enumerates the fields that can trigger an event (status, name, legal form, address, registration number), which clearly separates it from lookup_companies or enrich_company.

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?

Explicitly routes the agent: 'for the field detail, compare two lookups' names the alternative approach when per-field diffs are needed. It also sets expectations for the empty case. It does not explicitly say when to prefer this over a plain lookup, but the context is 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