Skip to main content
Glama

Получить цифровой паспорт компании по УНП или слагу

get_company_passport
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": {
      "identifier": "<identifier>"
    },
    "name": "get_company_passport"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoФормат ответа: структурированный json или готовый markdown-документ
identifierYes9 цифр УНП (например, 693300245) или слаг компании (например, 693300245-dadrio)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structure. The description still adds a non-obvious behavioral fact beyond them: only already-published passports are readable, which signals possible not-found cases. It stops short of describing the response body or error behavior.

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?

Two short sentences, front-loaded with the purpose, followed by the read-only scope constraint. Every clause carries information and nothing is padded.

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 simple two-parameter read tool with rich annotations this is close to sufficient, but with no output schema the description is the only place to learn what a "passport" actually returns, and it says nothing about its contents or size. An agent can call it, but cannot predict the payload.

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% and both parameters already document the format enum and the identifier forms with examples. The description restates the 9-digit УНП / slug rule but adds no format syntax, normalization rules, or fallback behavior 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?

States a specific verb and resource ("Получить проверяемый цифровой паспорт белорусской компании") plus the two accepted lookup keys (9-digit УНП or card slug), so the agent knows exactly what it fetches. It does not name or contrast any sibling (search_belarus_companies, verify_belarus_unp), leaving the choice between lookup-by-identifier and search-by-name to inference.

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?

The clause "только читает уже опубликованные паспорта" implies a precondition — the company must already have a published passport — which is useful usage context. However there is no explicit when-to-use vs the sibling search/verify tools, and no guidance on what to do when no passport exists.

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.