Skip to main content
Glama

Esef Entity Filings

esef_entity_filings
Read-onlyIdempotent

List every annual report one company has published to the XBRL International filings index, resolving a company name, LEI, or national registration number to the filer. Answers "what years has Citycon filed?" or "give me Nokia's latest annual report". Returns the resolved company (name, identifier, and how the match was made) plus each filing with period end, country, regime, validation error/warning counts and links to the xBRL-JSON, HTML report and viewer. Covers 25,640 filings in two regimes: ESEF (~16,000 annual financial reports from 19 European countries, AT BE CY CZ DK ES FI FR GB GR IS IT LT NL NO PL PT RO SE) and UAIFRS (~9,600 Ukrainian IFRS filings, country UA). Pass country or regime to pin the scope you mean. Portuguese (PT), Spanish (ES) and Norwegian (NO) ESEF reports are also read directly from where each country publishes them, CMVM for Portugal, CNMV for Spain, Oslo Børs NewsWeb for Norway, so PT, ES and NO coverage follows official publication (typically within a day) rather than the index's months-long lag; each row names its source and those rows carry the official published_at. Swedish (SE) reports are likewise read from Finansinspektionen (FI), the Swedish OAM, which is the only source for Swedish FY2025 reports, Belgian (BE) reports from the FSMA's STORI database, the Belgian OAM, Maltese (MT) reports from the Malta Stock Exchange OAM, the only source for Maltese FY2025 reports, Croatian (HR) reports from HANFA's SRPI, the Croatian OAM and the only source for Croatian FY2025 reports, Hungarian (HU) reports from the MNB's Közzétételek site, the Hungarian OAM and the only source for Hungarian FY2025 reports, Lithuanian (LT) reports from oam.lt, the Lithuanian OAM run by Nasdaq Vilnius, as well as the index, Romanian (RO) reports from the ASF OAM, the only source for Romanian FY2025 reports, Cypriot (CY) reports from the Cyprus Stock Exchange public OAM, the only source for Cypriot FY2025 reports, and Latvian (LV) reports from CSRI, the Latvian OAM, the only source for Latvian FY2024 and FY2025 reports. Luxembourgish (LU), Slovenian (SI) and Estonian (EE) reports are also answered directly from the LuxSE OAM, SEOnet or the Estonian FSA's OAM for each request, because these three OAMs' terms require the operator's consent for commercial reuse of their documents beyond ordinary access; a lookup made once on a caller's behalf is not that. Greek (GR) and Irish (IE) reports are likewise answered directly from Euronext Athens and the Euronext Dublin OAM for each request, these two sites' terms forbid bots and automated access outright rather than just reuse, so these are Bruce-authorized live lookups rather than a re-derivation of the usual reasoning, kept live and never mirrored for the same reason. Bulgarian (BG) reports are answered directly from BEIS, a Bulgarian disclosure agent whose terms ask only for attribution (unlike Bulgaria's other disclosure agents, which this pack does not call) and covers only the roughly three issuers that use it. None of GR/IE/BG carry machine-readable facts (esef_filing_facts declines a live-lookup id and points at its package_url/source_url); SI is limited to the ~20 most recent Slovenian annual-report announcements; IE rows carry no period_end (Irish fiscal year ends vary by issuer); GR's period_end is inferred from the filing's reporting year, not stated exactly, and flagged period_end_inferred. All six (LU, SI, EE, GR, IE, BG) are pinned-country lookups only, pass country explicitly. The same annual report is frequently indexed once per language edition (a Finnish and an English row for one financial year), so results are also grouped into distinct reports with the English edition preferred, and both a filing count and a distinct-report count are returned.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": "Nokia"
    },
    "name": "esef_entity_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFilings to return, 1-100. Default 50.
entityYesCompany name ("Citycon", "Nokia"), 20-character LEI ("549300P8N0P6KDGTJ206"), or national registration number for Ukrainian filers ("32033791"). Names are matched case-insensitively as a substring; the response says exactly which filer was chosen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "entity": "Nokia"
      -  },
      -  {
      -    "entity": "549300P8N0P6KDGTJ206"
      -  },
      -  {
      -    "entity": "259400A8SZP10GB5IB19"
      -  }
      -]New value: +[
      +  {
      +    "entity": "Nokia"
      +  },
      +  {
      +    "entity": "Krka"
      +  },
      +  {
      +    "entity": "549300P8N0P6KDGTJ206"
      +  },
      +  {
      +    "entity": "259400A8SZP10GB5IB19"
      +  },
      +  {
      +    "entity": "Ryanair"
      +  },
      +  {
      +    "entity": "Vipom"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "entity": "Nokia"
      -  },
      -  {
      -    "entity": "549300P8N0P6KDGTJ206"
      -  }
      -]New value: +[
      +  {
      +    "entity": "Nokia"
      +  },
      +  {
      +    "entity": "549300P8N0P6KDGTJ206"
      +  },
      +  {
      +    "entity": "259400A8SZP10GB5IB19"
      +  }
      +]
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description only needed to add context — and it adds a great deal: source per country, freshness (PT/ES/NO typically within a day vs the index's months-long lag), which sources are the only one for FY2025, which rows carry `published_at`, and specific data gaps (GR/IE/BG carry no machine-readable facts, SI limited to ~20 recent announcements, IE rows lack `period_end`, GR's `period_end` is inferred and flagged). The language-edition de-duplication behavior with English preferred, and the dual filing/distinct-report counts, are exactly the kind of behavioral disclosure annotations cannot provide.

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

Conciseness2/5

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

The first two sentences are well front-loaded, but the remainder is a single ~500-word run-on paragraph enumerating every national OAM, its legal terms, and its FY coverage. Most of that country-by-country inventory does not help an agent decide whether or how to call the tool, and the wall-of-text format buries the few genuinely actionable constraints.

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?

For a tool with this much source heterogeneity, the description does explain coverage, freshness, and data-quality caveats thoroughly, and there is no output schema so return values need spelling out (which it does). However, it is simultaneously over-complete on per-country provenance and incomplete on the actual callable surface, since the `country`/`regime` scoping it insists on has no corresponding schema field.

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 100% for the two declared parameters (`entity`, `limit`), so the baseline is 3, and the description adds little for `entity` beyond restating the accepted identifier forms. More seriously, it repeatedly instructs the caller to "pass `country` or `regime`" and "pass `country` explicitly," yet neither parameter exists in the input schema, which would send an agent chasing arguments it cannot supply.

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 opening sentence gives a specific verb and resource (list annual reports published to the XBRL International filings index) plus the resolution behavior (name, LEI, or national registration number to filer). The example questions ("what years has Citycon filed?", "give me Nokia's latest annual report") make the scope unmistakable and separate it from esef_search_filings and esef_filing_facts.

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?

It gives clear usage context through example queries and tells the caller to pass `country` or `regime` to pin scope, and that the six live-lookup countries are pinned-country lookups only. It also notes that esef_filing_facts declines live-lookup ids and points at `package_url`/`source_url`, which implicitly routes fact lookups elsewhere. It never explicitly contrasts itself with esef_search_filings or resolve_entity, so sibling selection is left partly to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.