ariregister-mcp

Get classifier

get_classifier

Read-only

Retrieves Estonian e-Business Register code lists so you can decode returned legal-form, status, role, country, contact-type, and currency codes into readable labels.

Instructions

Code lists used by the register (XML service, needs contract username and password), e.g. OIGVORMID (legal forms), EVSTAATUSED (company statuses), ISIKROLLID (person roles), RIIGID (countries), SIDEVAH (contact types), VALUUTAD (currencies). Use it to decode codes returned by the other tools.

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": {
      "classifier": "<classifier>"
    },
    "name": "get_classifier"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Language of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
`classifier`	Yes	Classifier code, e.g. 'OIGVORMID'.

Output Schema

Name	Required	Description	Default
`classifiers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a genuinely important operational fact: this is an XML service that requires contract username and password. That auth prerequisite is not derivable from the schema or annotations. It does not mention rate limits, failure modes, or freshness of the code lists.

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 what the resource is, then the use case. The six-code example list is long but is the main thing that lets an agent pick the right classifier value, so it earns its place; the parenthetical auth note is slightly buried mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be explained, and annotations cover the safety profile. The definition supplies the remaining essentials: what the codes are, an auth requirement, and when to call it. Nothing needed for correct invocation is missing.

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 would be 3, but the description adds meaning the schema lacks: it maps classifier codes to their real-world semantics (legal forms, company statuses, person roles, countries, contact types, currencies). The language parameter's effect is left entirely to the schema.

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 states concretely that this returns code lists used by the register and gives six named classifiers (OIGVORMID, EVSTAATUSED, ISIKROLLID, RIIGID, SIDEVAH, VALUUTAD), which makes the resource unambiguous. It implicitly distinguishes itself from siblings by framing the output as reference/decoder data rather than company records, though it never names an alternative tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it to decode codes returned by the other tools' gives a clear trigger for invocation relative to the rest of the toolset. It gives no explicit when-not condition or prerequisite ordering, so it stops short of full routing guidance.

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

Deploy Server