Skip to main content
Glama

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

Источники записей реестров

list_sources
Read-only

Список около 100 официальных реестров, по которым доступны сами записи (лицензии, СРО, аккредитации, реестры Банка России, ФНС, Ростехнадзора, Минпромторга): id, ведомство, число записей, дата выгрузки. Official Russian state registries with record-level data (licenses, SRO memberships, accreditations, Bank of Russia lists): id, agency, record count, snapshot date. Бесплатно, без ключа.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoТип: лицензия, СРО, аккредитация, реестр, разрешение
queryNoЧасть названия или id: «лицензия», «СРО», «cbr»
agencyNoЧасть названия ведомства: Банк России, Ростехнадзор

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the catalog size (~100), that it is free and requires no API key ('Бесплатно, без ключа'), and exactly which fields come back (id, agency, record count, snapshot date). It does not mention whether the list is paginated or cached, which keeps it from 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.

Conciseness3/5

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

The content is front-loaded and the enumerations are useful, but the entire text is duplicated verbatim in Russian and English, roughly doubling the length without adding information. The trailing 'Бесплатно, без ключа' is valuable but appears only at the very end.

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, zero-required-parameter read-only listing tool with no output schema, the description covers scope, contents, and access requirements, and it names the returned fields, which compensates for the missing output schema. However, it says nothing about the available filters or result size limits, which an agent needs to call it well.

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%, so the meaning of kind, query, and agency is already fully documented in the schema. The description does not mention filtering at all, so it adds no semantics beyond structured data — the 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?

The description states a specific verb and resource: a list of ~100 official Russian state registries for which record-level data is available, with concrete examples (licenses, SRO, accreditations, Bank of Russia, FNS, Rostekhnadzor, Minpromtorg). It even scopes the resource ('по которым доступны сами записи'), which implicitly separates it from registries without record data. It stops short of naming a sibling such as search_registries, so it is clear but not sibling-differentiated.

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 discovery/catalog step before calling get_registry or query_registry, since the tool returns ids and record counts. There is no explicit 'use this when…' statement, no exclusion of alternatives like search_registries or list_agencies, and no ordering guidance.

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.