Skip to main content
Glama

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

Допуски компании по ИНН

check_permits
Read-only

Все лицензии, членство в СРО, аккредитации, записи в реестрах Банка России, РНП и других отраслевых реестрах по ИНН (около 100 официальных источников). По каждому источнику found, записи со статусом, номером и датами, ссылка на первоисточник и дата выгрузки. All licences, SRO memberships and accreditations of a Russian company by INN across ~100 official registries. Без ключа 30 запросов в сутки (общий лимит с query_registry) и до 10 строк на источник; с ключом расходует лимит ключа.

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

Input Schema

NameRequiredDescriptionDefault
innYesИНН: 10 или 12 цифр
sourcesNoНеобязательно: id источников через запятую

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing a shared daily quota with query_registry, a 10-row-per-source truncation cap when unkeyed, key-based quota consumption, and the shape of each source's result (status, number, dates, primary-source link, export date). These are exactly the operational traits an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the entire substance is stated twice, once in Russian and once in English, with the quota details appearing only in the Russian half. The duplication costs length without adding information for an agent.

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 no output schema, the description usefully enumerates returned fields and the truncation behaviour, and annotations cover the read-only, external-call profile. Minor gaps remain: no mention of empty-result behaviour or how source ids relate to list_sources.

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%, so both inn (10 or 12 digits) and sources (comma-separated source ids) are already documented in the schema. The description adds only the framing of ~100 official sources, with no extra detail on source id syntax or format; 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 concrete verb+resource+scope: all licences, SRO memberships, accreditations and registry entries for a Russian company by INN across ~100 official sources, and enumerates the returned fields. It is clear what the tool does, though it never explicitly contrasts itself with lookalike siblings such as query_registry or check_inn.

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 context is limited to quota mechanics: 30 requests/day without a key, shared with query_registry, and key consumption if a key is present. There is no explicit statement of when to pick this tool over query_registry, check_inn or search_registries, so selection guidance is only implied.

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.