Skip to main content
Glama

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

Записи одного реестра

query_registry
Read-only

Найти записи в одном официальном реестре (id из list_sources) по ИНН, номеру лицензии или свидетельства, либо части названия. В ответе статус, номер, даты, ссылка на первоисточник и дата выгрузки. Look up records in one official registry by INN, licence number or part of the name; every answer carries the source URL and snapshot date. Без ключа 30 запросов в сутки и до 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": {
      "source": "<source>"
    },
    "name": "query_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
innNoИНН: 10 или 12 цифр
nameNoЧасть названия организации, от 3 символов
limitNoСтрок в ответе (без ключа не больше 10)
numberNoНомер записи точно как в реестре
sourceYesid источника из list_sources, например nostroy, cbr-mfo, fsrar-license, gisp-pp719
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/openWorld annotations: quota behavior (30 requests/day and max 10 rows without a key, more with a free key) and the shape of each answer (status, number, dates, source URL, snapshot date). Quota and provenance details are exactly the operational facts an agent needs before committing to a call.

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 lookup criteria and quota are front-loaded well, but the English sentence largely duplicates the Russian one, doubling length without adding new facts. The structure is logical, yet a third of the text is restatement.

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 6-parameter read tool with no output schema, the description covers search keys, quota limits, and returned fields, which is close to what an agent needs. It omits how multiple criteria are combined and whether results are ordered or paginated beyond `limit`.

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 already 83%, so the schema documents inn, name, number, limit and source itself. The description only restates which keys can be searched and does not explain whether criteria combine (AND vs OR) or how limit interacts with the anonymous cap beyond repeating the 10-row figure.

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 with scope: 'Найти записи в одном официальном реестре (id из list_sources)' and names the three lookup keys (INN, licence/certificate number, partial name). The 'one registry' scoping implicitly distinguishes it from a cross-registry search, but no sibling is named explicitly, so it falls short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear preconditions: the `source` id must come from list_sources, and the tool covers single-registry lookups by identifier or name fragment. It does not state when to prefer search_registries or check_inn instead, so there is no exclusion 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.