tvrtke

search_true_owners

Search across the Croatian Registry of True Owners (RSV) to discover all companies and legal entities associated with a specific individual owner or representative. RULES: Never invent personal identities, birth details, or corporate connections. If criteria are missing, interview the user first.

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

Input Schema

Name	Required	Description
`city`	No	Optional match on city / municipality
`limit`	No	Number of results (default 20, max 100)
`offset`	No	Pagination offset
`last_name`	No	Last name of the true owner or representative
`first_name`	No	First name of the true owner or representative
`citizenship`	No	Citizenship / nationality (e.g. Hrvatska)
`company_name`	No	Optional partial match on company name
`birth_month_year`	No	Birth month and year in format MM.YYYY (e.g. 02.1974)
`residence_country`	No	Country of residence (e.g. Hrvatska)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It adds a meaningful behavioral constraint ('Never invent personal identities, birth details, or corporate connections'), which is genuine value beyond the schema, but says nothing about result shape, pagination behavior, or data-freshness limits that an agent would want before invoking a registry lookup.

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 purpose and followed by operating rules; nothing is padded. The rules sentence is somewhat generic but does earn its place given the absence of annotations.

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, zero-required search tool with no output schema, the description adequately frames the domain and flags the need to gather criteria, but does not convey what a result contains or how limit/offset pagination behaves. It is minimally sufficient rather than complete.

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 description coverage is 100%, so every parameter is already documented in the schema, giving a baseline of 3. The description refers only vaguely to 'criteria' and adds no format or matching details beyond what the schema fields already state.

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 (search) and resource (Croatian Registry of True Owners / RSV) and clarifies the direction of the lookup: discovering companies tied to an individual owner or representative, which separates it from company-centric siblings like search_companies or get_company_true_owners. It stops short of naming those siblings explicitly.

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 rule 'If criteria are missing, interview the user first' gives one clear usage condition, but there is no guidance on when to prefer this over search_companies, nor when NOT to use it. Usage is implied rather than fully specified.

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

All tvrtke tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?