egrul-mcp

lookup_inn_by_passport

Read-only

ИНН физлица по паспортным данным через сервис ФНС. Требует точных персональных данных человека (ФИО, паспорт, дата рождения) — использовать только с явного согласия/по поручению самого человека, не для слежки за третьими лицами.

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": {
      "passport": "<passport>",
      "passport_date": "<passport_date>",
      "lastname": "<lastname>",
      "firstname": "<firstname>",
      "birthday": "<birthday>"
    },
    "name": "lookup_inn_by_passport"
  }
}

Input Schema

Name	Required	Description
`birthday`	Yes	Дата рождения, дд.мм.гггг или yyyy-mm-dd.
`lastname`	Yes	Фамилия.
`passport`	Yes	Серия и номер паспорта, 10 цифр без пробелов.
`firstname`	Yes	Имя.
`middlename`	No	Отчество (необязательно).
`passport_date`	Yes	Дата выдачи паспорта, дд.мм.гггг или yyyy-mm-dd.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: the external FNS dependency and a data-handling/consent constraint that annotations cannot express.

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

Conciseness5/5

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

Two sentences, zero filler, with the core purpose front-loaded and the constraint following. Nothing extraneous and nothing important buried.

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 read-only external lookup with full schema coverage and no output schema, the description covers purpose, required inputs, source, and legal/ethical limits. It could briefly note what is returned (the INN) but is otherwise complete.

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 every parameter (including formats and the 10-digit passport pattern) is already documented. The description only restates the same fields (ФИО, паспорт, дата рождения) without adding syntax or format detail, matching the baseline 3.

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+resource: obtain an individual's INN from passport data via the FNS service. It clearly distinguishes this from the many sibling check_* tools, though it never names a sibling explicitly. Purpose is unambiguous to an agent.

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 explicit usage conditions: requires exact personal data and must be used only with the person's consent or on their behalf, and not for surveilling third parties. This covers when-to-use and when-not-to-use, but names no alternative tool for adjacent needs.

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

All egrul-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?