Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

Check e-invoice recipients

check_einvoice_recipients
Read-only

Check whether companies are registered e-invoice recipients by Estonian registry code, so you can send machine-readable invoices through an operator; returns status OK or MR.

Instructions

Check whether companies are in the e-invoice recipient register, i.e. whether you can send them a machine-readable e-invoice through an operator. Public, no account needed. Status OK = has a valid link in the e-invoice register (operator in service_provider), MR = registry code not found in the e-invoice register.

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_codes": "<registry_codes>"
    },
    "name": "check_einvoice_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1).
include_namesNoAlso return company names (default false).
registry_codesYes1–100 registry codes.

Output Schema

NameRequiredDescriptionDefault
pagesYes
recipientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new context: no authentication is required, and it decodes the result states (OK = valid register link with operator in `service_provider`; MR = registry code not found). It does not mention rate limits or batch-size behavior, which the schema covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and its real-world meaning, then auth preconditions, then result-code decoding. No filler or redundancy.

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, yet the description still explains the key status values an agent needs to interpret results. Combined with the no-account-needed note and the batch semantics inherited from the schema, an agent has everything required to call and interpret this 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?

Schema description coverage is 100%, so all three parameters are already documented, including the 8-digit registry code format, the 1–100 batch limit, and the `search_companies` cross-reference. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('check whether companies are in the e-invoice recipient register') and immediately clarifies the real-world meaning: whether a machine-readable e-invoice can be sent via an operator. This is unmistakably distinct from the sibling tools (search_companies, get_company, etc.), which deal with company data rather than e-invoice eligibility.

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?

The use case is clearly implied by 'whether you can send them a machine-readable e-invoice through an operator', and the precondition 'Public, no account needed' removes an auth question. There are no explicit exclusions or named alternatives, so it stops short of a 5.

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