Skip to main content
Glama

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

Паспорт реестра

get_registry
Read-only

Паспорт реестра по id из search_registries: ведомство, закон и статья, год появления, открытость, есть ли API и открытые данные, официальный сайт, где проверить запись, ссылка на подробную карточку на reestr-reestrov.ru.

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": {
      "id": "<id>"
    },
    "name": "get_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid реестра, например egrul, groro

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety is covered. The description goes further by listing precisely which fields come back (agency, law/article, year, openness, API presence, site, verification location, card link), which is meaningful because no output schema exists. It does not state what happens for an unknown id.

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?

One sentence, front-loaded with the verb and the key constraint, then a tight enumeration of returned fields. The field list is long but each item earns its place by substituting for a missing output schema.

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 read-only lookup with no output schema, the description covers entry point, returned content, and the source-of-truth site. Only minor gaps remain: invalid-id behavior and differentiation from query_registry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 100% schema coverage with example values (egrul, groro), so the baseline is 3. The description adds provenance — that the id should come from search_registries — which is genuinely new information not present in the schema.

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+resource ("Паспорт реестра по id") and enumerates the recorded attributes (ведомство, закон/статья, год, открытость, API, сайт), so the agent knows exactly what a 'passport' contains. It ties itself to search_registries as the ID source, but does not distinguish itself from query_registry, which is the closest ambiguous sibling.

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?

"по id из search_registries" implies the workflow: search first, then fetch details by ID. However there is no explicit when-not guidance and no statement of how this differs from query_registry, so the agent must infer the boundary between looking up metadata about a registry versus querying its data.

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.