Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

EU annual report financials (ESEF)

get_eu_annual_reports
Read-only

Retrieve audited annual financials for European listed companies by company name or LEI, including revenue, profit, margins, balance sheet, cash flow and dividends from ESEF reports.

Instructions

Audited annual financials of European listed companies, from their official ESEF annual reports (source: filings.xbrl.org; EU/EEA, UK and Ukraine, about 27,600 reports from 28 countries; Germany is not covered). Use it for revenue, profit, margins, EPS, balance sheet, cash flow or dividends of a listed European company.

Pass exactly one of `lei` (most precise) or `company` (case-insensitive part of the
registered name; it can match several companies, so check `company_name`). `countries`
narrows a name search. Newest fiscal year first.

Returns one row per annual report: lei, company_name, country, period_end, currency,
revenue, gross_profit, operating_profit, ebitda, net_income, eps_basic/diluted,
total_assets, total_equity, total_liabilities, cash_and_equivalents, operating_cash_flow,
dividend_per_share, operating_margin, net_margin, return_on_equity, equity_ratio,
revenue_growth, prior_year (same metrics for the comparative year) and viewer_url (cite
it: the report page where every value can be checked). Money is in full units of
`currency`; ratios are decimals (0.25 = 25%). A missing metric was not tagged in the
report; never treat it as zero.

Cost to the user: $0.05 per annual report (with APIFY_TOKEN plus $0.01 per call). Takes
about 10-60 s.

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

Input Schema

NameRequiredDescriptionDefault
leiNo20-character Legal Entity Identifier
companyNoPart of the name, e.g. "heineken"
countriesNoISO alpha-2 filing countries, e.g. ['NL']
max_resultsNoMax annual reports to return (1-10).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnly/openWorld hints it discloses pricing ($0.05 per report plus $0.01 per call with APIFY_TOKEN), latency (10-60 s), sort order (newest fiscal year first), and grain (one row per annual report). It also warns that an untagged metric is missing rather than zero, and that viewer_url should be cited for verification — exactly the behavioral context annotations cannot carry.

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?

Front-loaded with purpose, coverage and exclusion, then parameter rules, then output units and cost — a sensible order with no filler sentences. The long enumeration of returned fields partially duplicates the existing output schema and could be trimmed without losing meaning.

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?

Covers everything an agent needs for this call: coverage gaps, key selection, interpretation of money units and decimal ratios, missing-value semantics, citation guidance, cost and latency. Return-field detail is somewhat redundant given the output schema, but nothing essential is absent.

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 already 100%, yet the description adds real meaning: `lei` is the most precise key, `company` is a case-insensitive name fragment that can match multiple companies (so check `company_name`), and `countries` is only a narrowing filter for name search. Only `max_results` is left to the schema alone, which is appropriate.

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 verb and resource ('Audited annual financials of European listed companies, from their official ESEF annual reports'), names the source domain, quantifies coverage (27,600 reports, 28 countries, EU/EEA/UK/Ukraine) and explicitly excludes Germany. An agent knows exactly what this retrieves and can distinguish it from SEC-oriented siblings.

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?

Gives a clear use-case list (revenue, profit, margins, EPS, balance sheet, cash flow, dividends) and explicit parameter-selection rules: pass exactly one of `lei` or `company`, with `countries` narrowing a name search. It lacks direct routing against likely alternatives such as get_company_accounts or find_sec_company, so it stops short of full when-not/alternative guidance.

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