Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

List company documents

list_company_documents
Read-only

List an Estonian company's public file documents by registry code, including annual reports (PDF, BDOC/DDOC, XBRL) and articles of association, with e-Business Register links.

Instructions

Documents in a company's public file (XML service, needs contract username and password): annual reports as PDF, BDOC/DDOC and XBRL, and articles of association, with their e-Business Register URLs (opening one needs a login there; this tool never requests the paid access token that would buy the document). Document types: A = annual report PDF, D = BDOC/DDOC, X = XBRL, P = articles of association. Report types: A = annual, V = interim, L = liquidation, P = final.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
yearNoReporting year.
validNoK = valid, A = expired.
languageNoLanguage of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
document_typeNo
registry_codeYes8-digit Estonian registry code (registrikood), e.g. 14663023. Find it with search_companies.

Output Schema

NameRequiredDescriptionDefault
pagesNo
documentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already declaring the safety profile, the description adds real context beyond annotations: the contract-credentials requirement, the fact that returned URLs need a separate login, and the deliberate exclusion of the paid access token flow. That materially informs the agent about what it will and won't get, though pagination/result-size behavior is unmentioned.

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

Conciseness3/5

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

The core statement is front-loaded, but the single run-on paragraph mixes resource description, auth warnings, two enum legends, and URL caveats. The report-type legend is surplus given the schema has no corresponding parameter and should be cut or reconciled.

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?

An output schema exists, so return values need not be explained, and auth requirements are covered. Still missing: how paging works, what happens when no documents exist, and whether the report-type legend corresponds to anything callable — gaps that matter for a 6-parameter open-world 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 coverage is 67%, and the description does usefully decode document_type (A/D/X/P), which the schema leaves as a bare enum. But it spends equal space on a 'Report types: A/V/L/P' legend that maps to no parameter in the schema, which can mislead an agent into thinking such a filter exists, while page and the year/valid semantics get no elaboration.

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 names a concrete resource and scope — 'Documents in a company's public file' — and enumerates the formats returned (annual reports PDF, BDOC/DDOC, XBRL, articles of association) plus URLs. It does not distinguish itself from the very close sibling list_annual_reports, so an agent cannot tell from the text alone which of the two to call.

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?

Prerequisites are given (XML service, contract username and password, opening URLs requires a login there) and it explicitly notes it will not request the paid access token, which is useful when-to-use context. However, there is no explicit guidance on choosing this tool over list_annual_reports or get_company, nor on 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.