AI-BELARUS — Belarus business registry

Company card by UNP (stored)

lookup_company

Read-onlyIdempotent

Collected public card of a Belarusian business entity by UNP (9 digits): legal name, status, each statement with registry source, retrieval time and sha256 of the raw response; withheld fields with reasons. Instant, no registry call. Карточка субъекта по УНП из собранного.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`unp`	Yes	УНП субъекта — РОВНО 9 цифр (из документов, ЕГР или ГРП). Иное отклоняется с invalid_unp.

Output Schema

TableJSON Schema

Name	Required	Description
`unp`	No	УНП, 9 цифр
`card`	No	Публичная проекция: утверждения с источником, временем и sha256
`page`	No	Ссылка на карточку (только если это юрлицо)
`error`	No	Отказ: code (напр. invalid_unp) и detail
`found`	No	Найдена ли карточка в собранном
`meaning`	No	Пояснение смысла, когда не найдено (НЕ значит «не существует»)

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 15, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / unp / description

Added value: +"УНП субъекта — РОВНО 9 цифр (из документов, ЕГР или ГРП). Иное отклоняется с invalid_unp."

removedInput schema / properties / unp / title
```
Removed value: -"Unp"
```

removedInput schema / title

Removed value: -"lookup_companyArguments"

addedOutput schema / description

Added value: +"Карточка из собранного, либо «не найдено», либо отказ (error)."

addedOutput schema / properties

Added value: +{
+  "card": {
+    "additionalProperties": true,
+    "description": "Публичная проекция: утверждения с источником, временем и sha256",
+    "type": "object"
+  },
+  "error": {
+    "additionalProperties": true,
+    "description": "Отказ: code (напр. invalid_unp) и detail",
+    "type": "object"
+  },
+  "found": {
+    "description": "Найдена ли карточка в собранном",
+    "type": "boolean"
+  },
+  "meaning": {
+    "description": "Пояснение смысла, когда не найдено (НЕ значит «не существует»)",
+    "type": "string"
+  },
+  "page": {
+    "description": "Ссылка на карточку (только если это юрлицо)",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "unp": {
+    "description": "УНП, 9 цифр",
+    "type": "string"
+  }
+}

removedOutput schema / title

Removed value: -"lookup_companyDictOutput"

First observedSep 24, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: it is instant because it makes no registry call, and it discloses that results come from a stored collection with per-statement registry source, retrieval time, sha256 of the raw response, and withheld fields with reasons.

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 English portion is front-loaded with purpose, then the returned content, then the key latency fact ('Instant, no registry call'). The trailing Russian sentence ('Карточка субъекта по УНП из собранного') duplicates the English purpose and does not earn its place.

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?

With an output schema present, return values need not be enumerated, yet the description usefully sketches them plus provenance and withholding behavior. The only real gap is the absence of routing guidance against the four sibling tools, which is a usage concern rather than a completeness one.

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 'unp' parameter is fully documented in the schema, including the 9-digit constraint and invalid_unp rejection. The description repeats the 9-digit requirement rather than adding syntax or format meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: retrieving a collected public company card for a Belarusian entity keyed by UNP. The scope is well bounded ('by UNP (9 digits)', 'Collected public card'), which separates it from search_companies, but no sibling tool is named or contrasted, so an agent must infer the boundary from the input alone.

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?

Usage is only implied: the tool requires a known UNP, so it is the lookup path once an identifier is in hand. There is no explicit statement of when to prefer it over check_counterparty, entity_timeline, or search_companies, and no exclusions or prerequisites are given.

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

All AI-BELARUS — Belarus business registry 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?