Skip to main content
Glama
ariregister-mcp

ariregister-mcp

by aanndryyyy

List annual reports

list_annual_reports
Read-only

Retrieve a company's filed annual reports by registry code or year, including submission dates, revenue, balance-sheet totals, employee counts, audit status, and report file links.

Instructions

Annual reports filed by a company (REST, needs an API key): year, submission date, revenue, balance-sheet total, employee count, audit status, and links to the report files (PDF, BDOC/DDOC, XBRL). For the actual balance-sheet and income-statement lines use get_annual_report_figures.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1).
yearNoReporting year.
languageNoLanguage of classifier texts (statuses, roles, legal forms): 'eng' (default) or 'est'.
page_sizeNoResults per page, 1–1000 (default 100).
submitted_toNoSubmitted on or before this date-time (ISO 8601).
document_typeNoA = PDF, D = BDOC/DDOC, X = XBRL.
registry_codeNo8-digit Estonian registry code (registrikood), e.g. 14663023. Find it with search_companies.
submitted_fromNoSubmitted on or after this date-time (ISO 8601).

Output Schema

NameRequiredDescriptionDefault
listYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new operational context: this is a REST endpoint requiring an API key, which an agent needs before attempting a call. It does not mention pagination limits or rate limits, but those are largely captured by the schema.

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?

Two sentences, zero filler. The resource and returned fields come first, then the disambiguation to the sibling, which is the right ordering for an agent scanning for the correct tool.

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?

With an output schema present, the description need not explain return values, and the auth requirement plus sibling routing cover the main operational questions. A brief note on pagination behavior or default result volume would make it fully complete, but nothing essential is missing.

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 (page, page_size, year, language, submitted_from/to, document_type, registry_code) is already documented, including the pointer to search_companies for registry codes. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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?

States a specific resource and verb-equivalent ('Annual reports filed by a company') plus the exact field set returned, so an agent knows this is a metadata/list endpoint rather than a financials endpoint. It explicitly contrasts with the sibling get_annual_report_figures, which handles the actual statement lines.

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?

Explicitly routes the agent to get_annual_report_figures when balance-sheet or income-statement lines are wanted, which is the main ambiguity among siblings. It does not address when to prefer list_company_documents or other document tools, so guidance is clear but not exhaustive.

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