Skip to main content
Glama
atomno-labs

EGRUL MCP Server

get_full_card

Retrieve complete registration card for a Russian legal entity or entrepreneur, including details, OKVED codes, founders, and director, using INN or OGRN.

Instructions

Полная карточка (все секции: реквизиты, ОКВЭД, учредители, директор).

Хотя бы один из inn / ogrn обязателен. Если переданы оба — используется inn.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
innNo
ogrnNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that at least one of inn/ogrn is required and inn takes precedence, but does not mention read-only nature, authentication needs, or error handling for missing parameters.

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?

The description is two sentences and front-loads the purpose. It is concise with no unnecessary words, though structure could be improved with bullet points for clarity.

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?

Given the presence of an output schema and only two parameters, the description covers the primary requirements: purpose and parameter constraints. It lacks mention of error cases or usage limitations, but is largely complete for a simple tool.

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 input schema has 0% description coverage, but the description adds meaning by clarifying that inn and ogrn are alternative identifiers, at least one is mandatory, and inn is used if both are provided. This significantly compensates for the schema's lack of parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Full card (all sections: details, OKVED, founders, director)', clearly indicating it retrieves a complete company card. This distinguishes it from sibling tools like get_director and get_founders, which target specific sections.

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?

The description implies usage for retrieving full card data, but does not explicitly contrast with siblings or state when to use this tool over alternatives like search_by_inn or get_director. No exclusion criteria or context is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/atomno-labs/mcp-egrul'

If you have feedback or need assistance with the MCP directory API, please join our Discord server