Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

Get company data

get_company
Read-only

Fetch complete Estonian company record by registry code and select data blocks—general, related persons, commercial pledges, rulings, or registry cards—with include.

Instructions

Full register data for one company (REST, needs an API key). Choose blocks with include: general (names, addresses, legal form, share capital, financial year, contacts, EMTAK activities, VAT number), related_persons (board and council members, shareholders, representation rights), commercial_pledges, rulings (court registry rulings), registry_cards (entries on the registry card). Default: general. Company status codes: R = registered, L = in liquidation, N = bankrupt, K = deleted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "registry_code": "<registry_code>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoData blocks to return (default ['general']).
languageNoLanguage of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
only_validNoOnly current data (default true). False includes historical entries.
registry_codeYes8-digit Estonian registry code (registrikood), e.g. 14663023. Find it with search_companies.

Output Schema

NameRequiredDescriptionDefault
urlYes
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Beyond that, the description adds meaningful context: REST access requires an API key, include blocks control returned data, default is general, and status codes are defined. It does not cover rate limits or error behavior, but those are secondary for a read-only lookup tool.

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?

The description is front-loaded with purpose and access requirements, then explains include blocks and defaults. The long parenthetical block list is dense but necessary. There is little wasted wording, though readability could be improved with lighter structure.

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?

Given an output schema and full input schema coverage, the description supplies the key context an agent needs: purpose, API key requirement, block selection semantics, defaults, and status code meanings. Remaining gaps are minor because parameter details such as language and only_valid are fully documented in the schema.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining what each include block contains, which the schema only names, and by giving status-code meanings. It does not add detail for language or only_valid beyond the schema, so it is not a 5.

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 clearly states a specific verb and resource: retrieving full register data for one company. It also lists the include blocks, which makes the scope concrete. However, it does not explicitly differentiate itself from sibling tools such as get_beneficial_owners or get_representation_rights.

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: use this when you have a registry code and need register data for one company. The description explains the include mechanism and default block, but it does not state when to prefer this tool over specialized siblings or when not to use it.

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