Skip to main content
Glama

check_for_red_flags

Identify red flags for a Russian counterparty through 8 checks including mass address, disqualified directors, bankruptcy, tax debts, and active lawsuits. Flags errors without failing other checks.

Instructions

Агрегированный риск-чек по контрагенту (8 проверок, SPEC §3.5).

Базовые 4 проверки (всегда):

  • mass_address — массовый юр.адрес ФНС;

  • mass_director — массовый руководитель (≥10 действующих компаний);

  • disqualified_director — руководитель в реестре дисквалифицированных;

  • bankruptcy_records — активные дела в ЕФРСБ.

Расширенные 4 проверки (include_extended=True):

  • tax_debts — индикатор задолженности по налогам (Прозрачный бизнес);

  • no_reporting — нет налоговой отчётности > 1 года (Прозрачный бизнес);

  • enforcement_proceedings — открытые исп.производства (Банк данных ФССП);

  • active_lawsuits — активные арбитражные дела где контрагент ответчик (КАД), фильтр по сумме иска через lawsuits_threshold_rub.

Любая внешняя проверка может вернуть ошибку (CAPTCHA, 5xx, timeout) — она попадёт в errors[] и не сорвёт остальные проверки.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
innYesИНН контрагента (10 или 12 цифр).
include_extendedNoзапускать ли расширенные 4 проверки. По умолчанию True.
lawsuits_threshold_rubNoпорог фильтра арбитражных дел в рублях. По умолчанию 1 000 000 ₽ (отсечь мелкие споры).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations, so description carries full burden. Discloses possible errors (CAPTCHA, 5xx, timeout) and that errors are collected without failing other checks. Reveals behavioral traits beyond annotations.

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?

Well-structured with bullet points for readability, but slightly lengthy. Front-loaded with purpose. Could be slightly more concise.

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?

Covers purpose, parameter details, error handling, and references SPEC. Output schema exists, so return values are handled. Adequate for a tool with 8 sub-checks and error handling.

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?

Input schema has 100% coverage, but description adds value by listing the specific checks controlled by include_extended and explaining the lawsuit filter threshold.

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?

Clearly states it performs a aggregated risk check with 8 checks, referencing SPEC §3.5. Differentiates from siblings like check_contractor, check_inn by being comprehensive.

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?

Explains basic vs extended checks with include_extended, and describes error handling. Does not explicitly contrast with sibling tools, but context is clear when to use.

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-fns-check'

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