Skip to main content
Glama

Merit — Ukrainian Law & Registers

Search Enforcement Proceedings

ua_enforcement_proceedings__search
Read-onlyIdempotent

АСВП, Ukraine's register of enforcement proceedings (виконавчі провадження).

Wider than ЄРБ (ua_debtors): it keeps closed ('Завершено') and refused ('Відмовлено у відкритті') proceedings too. The shared key is vp_num.

debtor_code is published for legal entities only, about 9% of rows. The source carries no identifier at all for a natural-person debtor, so a null code means the source publishes none, not that parsing failed.

A date later than the snapshot, or a birth date before 1900, is a source typo: served null, sorted and filtered as undated, its published value in *_invalid.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ua_enforcement_proceedings__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPrefix of the debtor's name.
limitNo
offsetNo
vp_numNoExact proceeding number.
opened_toNoInclusive ISO date.
birth_dateNoExact YYYY-MM-DD; tells namesakes apart. Needs q.
debtor_codeNoExact ЄДРПОУ; legal entities only.
opened_fromNoInclusive ISO date.
proceeding_stateNoExact state string as published.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / birth_date
      Added value: +{
      +  "description": "Exact YYYY-MM-DD; tells namesakes apart. Needs q.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses that `debtor_code` is published for only ~9% of rows and that a null means the source publishes none rather than a parse failure. It also explains how out-of-range dates are typed, nulled, sorted and filtered as undated, and preserved in `*_invalid`. Remaining gaps are return ordering and result shape, not behavior contradictions.

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?

Four tight sentences, each carrying a distinct fact (register identity, coverage contrast, debtor_code semantics, date-typo handling) with no filler. The lead is dataset identity rather than an explicit action statement, which is a minor front-loading weakness. Ukrainian source terms in parentheses are justified for a Ukrainian registry.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no output schema, the definition covers the two hardest interpretive traps (null debtor codes, invalid dates) but never describes what a result record contains, how results are ordered, or what `limit`/`offset` behavior yields. An agent can call it, but cannot predict the response payload from the description alone.

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?

With 78% schema coverage the baseline is 3, but the description adds real meaning beyond the schema: it explains that `debtor_code` is legal-entity-only and why nulls occur, and it defines the invalid-date handling for the date parameters (including the `*_invalid` companions that do not appear in the schema at all). It does not clarify `proceeding_state` value formatting or prefix vs exact behavior of `q` beyond the schema text.

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 first line names the exact register (АСВП, Ukraine's enforcement proceedings, виконавчі провадження) so the resource is unambiguous, and the second line distinguishes its coverage from ЄРБ via the shared `vp_num` key. It never states the verb 'search' outside the title, but the intent is unmistakable. No sibling 'lookup' counterpart is discussed, so differentiation is partial.

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 comparison 'wider than ЄРБ (ua_debtors): it keeps closed and refused proceedings too' implies a selection rule between the two registers. However, it never says when to use this versus `ua_enforcement_proceedings__lookup`, nor whether closed/refused proceedings are included by default or must be requested. Usage is implied rather than stated.

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.