Skip to main content
Glama

Digital Passport Belarus

Проверка контрольной суммы 9-значного УНП

verify_belarus_unp
Read-onlyIdempotent

Проверить математическую контрольную сумму 9-значного УНП Беларуси и определить регион регистрации.

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": {
      "unp": "<unp>"
    },
    "name": "verify_belarus_unp"
  }
}

Input Schema

NameRequiredDescriptionDefault
unpYes9 цифр УНП для проверки

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that a region is derived as part of the check, which is useful beyond the annotations, but it does not say what happens with an invalid checksum or how the region is reported. With annotations doing the heavy lifting, a 3 is appropriate.

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?

A single compact sentence with the resource and both outcomes front-loaded and no filler. It could be marginally clearer about the return value, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotation-rich validation tool this is close to sufficient, and it does flag the region output. However, with no output schema, the description should say more about what the verification result looks like (valid/invalid plus region), leaving a small but real gap.

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?

Only one parameter, and the schema already documents it at 100% coverage as '9 digits of UNP for verification'. The description merely restates the 9-digit constraint, adding no format rules (e.g. leading zeros, non-numeric input handling) beyond the schema. Baseline 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?

Names a specific verb+resource: verifies the mathematical checksum of a 9-digit Belarus UNP and also determines the registration region. This clearly separates it from the search/passport siblings, which retrieve company data rather than validate an identifier. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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: an agent can infer this is the tool for validating a UNP string before or instead of doing a lookup. There is no explicit statement of when to prefer it over search_belarus_companies or get_company_passport, and no note that it does not return company details.

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.