Skip to main content
Glama

Merit — Ukrainian Law & Registers

Search Ukrainian NSDC Sanctions

ua_sanctions__search
Read-onlyIdempotent

Ukraine's NSDC (РНБО) sanctions register: individuals, legal persons, vessels. q: name/alias words, all required; a code in q also matches identifiers. status: active, expired (term ended), excluded (cancelled). source.as_of = latest decree loaded.

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

Input Schema

NameRequiredDescriptionDefault
qNoName words; each must occur.
kindNo
limitNo
offsetNo
statusNo
identifierNoExact tax, registry, passport, IMO or MMSI number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description does add real behavioral context beyond them: the meaning of each `status` value (term ended vs cancelled) and that `source.as_of` reflects the latest decree loaded, which tells the agent about data freshness. It stops short of describing result shape or pagination behavior, so a 3 is right with annotations already covering safety.

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?

Three compact lines, front-loaded with the register identity and then the two parameters that carry non-obvious semantics. Nothing is wasted, though the telegraphic backtick-heavy style and the stray `source.as_of` reference (which is not an input parameter) read more like notes than prose.

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?

No output schema exists, and the description does not say what a match record contains beyond implying a `source.as_of` field. With six parameters and zero required ones, it also leaves unstated what happens on an empty request and how `limit`/`offset` paginate. Adequate for a lookup-style search, but not fully complete for a tool with this schema breadth.

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 only 33%, so the description has to carry weight: it explains that all words in `q` must occur and that a code in `q` also matches identifiers, plus the semantics of the three `status` values. It says nothing about `kind`, `limit`, `offset`, or when to use `identifier` instead of `q`; those gaps are partly self-evident from enums and defaults, so the added value is useful but partial.

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 a specific register ('Ukraine's NSDC (РНБО) sanctions register') and enumerates the covered entity types (individuals, legal persons, vessels). The verb is only implied by the tool name, and the sibling sanctions registers (eu_, ofac_, un_, uk_sanctions__search) are not explicitly differentiated, but the register scoping is clear enough to select the tool.

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 implied by the parameter semantics (use `q` for names, a code matches identifiers, use `status` to widen to expired/excluded), but there is no explicit when-to-use / when-not-to-use guidance and no mention of the parallel EU/OFAC/UN sanctions tools. The agent has to infer that this tool is specific to Ukrainian NSDC listings.

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.