Skip to main content
Glama

Merit — Ukrainian Law & Registers

Search Corruption Offenders Register

ua_corruption_registry__search
Read-onlyIdempotent

Ukraine's register of persons who committed corruption or corruption-related offences (НАЗК).

An entry records one offender, the offence, the article they were held liable under, the sanction, and the court decision or disciplinary decree that imposed it. Most entries are natural persons sanctioned by a court.

sentence_number, where present, is the decision's ЄДРСР id, so an entry can be checked against the decisions register itself.

This source publishes no freshness of its own, so as_of is mirror sync date.

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_corruption_registry__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text over name, offence, article, court and case.
limitNo
offsetNo
date_toNoInclusive ISO date.
date_fromNoInclusive ISO date.
entity_typeNoФізична особа or Юридична особа.
punishment_typeNoСудове рішення or Дисциплінарне стягнення.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: `as_of` is a mirror sync date rather than source freshness (an important data-quality caveat), and sentence_number is an ЄДРСР id enabling verification against the decisions register. Return format and pagination are not described.

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?

Front-loaded with the register's identity and scope, then entry anatomy, then two caveats (sentence_number provenance, as_of meaning). Every sentence adds information; only the sentence_number paragraph is slightly more detail than strictly needed to select the tool.

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?

With seven optional parameters, no output schema, and a read-only profile, the description does the right extra work by describing what an entry contains — effectively standing in for the missing output schema. Gaps remain around pagination, default result shape, and whether the date filters apply to offence, sanction, or sync date.

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 71%, so the baseline is 3. The description adds little about the seven parameters — date_from/date_to inclusive semantics, limit/offset, and the entity_type/punishment_type Ukrainian values are left entirely to the schema. The remark that most entries are natural persons gives mild context for entity_type filtering, but nothing more.

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 identifies a specific resource precisely: Ukraine's NАЗК register of corruption offenders, and enumerates what an entry contains (offender, offence, article, sanction, court decision/decree). This clearly separates it from the sanctions, debtors, and EDRSR siblings. It never states the search verb or that it is a filtered/queryable lookup, though the name and title carry that.

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?

Usage is only implied: an agent infers you use this to find corruption offenders, and the note that sentence_number is an ЄДРСР id hints at cross-checking against ua_edrsr__* tools. There is no explicit when-to-use, when-not, or named alternative among the many sibling registers.

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.