Skip to main content
Glama

Реестр реестров: Russian state registries

Проверка компании или ИП по ИНН

check_inn
Read-only

Проверка организации или ИП по ИНН в официальных реестрах в реальном времени: ЕГРЮЛ/ЕГРИП (название, ОГРН, статус, руководитель), реестр МСП, Федресурс (банкротство), реестр операторов персональных данных, реестр недобросовестных поставщиков, лицензии из выписки ЕГРЮЛ. Запрос идёт к сайтам ведомств, ответ до 30-60 секунд.

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": {
      "inn": "<inn>"
    },
    "name": "check_inn"
  }
}

Input Schema

NameRequiredDescriptionDefault
innYesИНН: 10 цифр (организация) или 12 (ИП)

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 readOnly and open-world, and the description adds real value on top: it discloses that the call goes to external agency websites in real time and that the response can take 30-60 seconds, plus which datasets are covered. It leaves failure/timeout behavior and partial-result handling unstated, keeping it short of a 5.

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?

Two sentences, front-loaded with the purpose and ending with the latency caveat, which is the right place for it. The long registry list is dense but each item signals returned data, so it earns its space, though the enumeration could be trimmed slightly.

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, no-output-schema lookup tool this is nearly complete: it covers scope, data sources, freshness, and latency. Only error/partial-result behaviour and output shape are missing, which matters given the multi-source aggregation.

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's 10-digit (organization) / 12-digit (ИП) format is already documented in the schema, so the description's 'по ИНН' restates rather than extends it. Baseline 3 applies since the schema carries the parameter burden.

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 and resource ('Проверка организации или ИП по ИНН') and enumerates the exact registries consulted (ЕГРЮЛ/ЕГРИП, МСП, Федресурс, etc.), so the agent knows precisely what data it gets back. It never names or contrasts with the generic registry siblings (query_registry, get_registry), so differentiation is inferred from the specificity rather than stated.

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?

Implies usage — you have an INN and need a live company check — but gives no explicit when-to-use versus get_registry/query_registry, and no when-not conditions or prerequisites beyond the INN format. The mention that the request hits agency websites hints at when live checking is warranted, but the agent must infer the routing decision.

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.