Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

Search trusts

search_trusts
Read-only

Search Estonian trust records by name, status, country or involved persons such as trustees, settlors and beneficiaries; returns current entries by default.

Instructions

Search the register of trusts and similar arrangements (REST, needs an API key): trust name, status, country and the people involved (trustee UH.HALDUR, settlor UH.LOOJA, beneficiary UH.SOODUST, …). Beneficial-owner details of a trust are not requested by this tool.

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": "search_trusts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
languageNoLanguage of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
page_sizeNoResults per page, 1–1000 (default 100).
only_validNoOnly current data (default true). False includes historical entries.
trust_nameNo
identity_codeNoPersonal identification code of a related person.
person_surnameNo
person_birthdayNo
person_first_nameNo

Output Schema

NameRequiredDescriptionDefault
listYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully adds that the source is a REST service requiring an API key — real behavioral context the schema doesn't carry. It also discloses a negative scope fact (beneficial-owner data is excluded), which prevents wasted calls. Beyond that it says nothing about rate limits, failure modes, or the difference between live and historical registers despite the only_valid flag, so it adds value but not depth.

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?

Two sentences, front-loaded with the action and followed by scope and the single exclusion — no filler. The parenthetical example role codes are informative but slightly noisy for a definition this short, and the 'status, country' mention adds words that don't map to any callable parameter.

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 annotations covering safety and an output schema covering return shape, the description's job is to establish scope, auth, and exclusions — all three are present. What remains thin is how the person-level filters interact with trust-level filters and what an unfiltered call returns, but those are secondary for a zero-required-parameter search tool.

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?

At 56% schema coverage the schema names five filter parameters but only describes four (page, page_size, language, only_valid), leaving trust_name, identity_code, person_surname, person_first_name and person_birthday undocumented. The description partially compensates by framing the people filters as trustee/settlor/beneficiary role lookups with example codes (UH.HALDUR, UH.LOOJA, UH.SOODUST), which helps an agent understand what the person fields target. It still doesn't tie those role examples to a specific parameter, nor explain how the person fields combine with trust_name.

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 and resource ('Search the register of trusts and similar arrangements') and enumerates what is searchable (trust name, status, country, people involved), which is far better than a tautology. It also carves out a boundary against the beneficial-owner sibling ('Beneficial-owner details of a trust are not requested by this tool'). Minor drag: 'status' and 'country' are described as searchable facets but do not exist as input parameters, so an agent may look for filters that aren't there.

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?

Provides an implicit when-not ('beneficial-owner details ... not requested by this tool') and a prerequisite ('needs an API key'), which is useful context. However, it never names the alternative tool to use for beneficial owners and gives no positive when-to-use guidance versus the other search_* siblings. The routing signal is inferential rather than explicit.

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