Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

UK, Danish and Norwegian company accounts

get_company_accounts
Read-only

Retrieve revenue, profit, equity, cash and employee figures for UK, Danish and Norwegian companies, including private ones, by registration number from official filings.

Instructions

Financials of UK, Danish and Norwegian companies, including private ones, from the accounts they file with Companies House (UK), Erhvervsstyrelsen (DK) and the Brønnøysund Register of Company Accounts (NO). Use it for revenue, profit, equity, cash or employees of a (private) company in these countries when you know its registration number.

Coverage: UK every year filed digitally (iXBRL; paper/PDF-only years are skipped, and small
UK companies often file no profit and loss account); Denmark all years; Norway the last 3
fiscal years (own accounts, not group).
Pass at least one registration number. Newest fiscal year first.

Returns one row per company per fiscal year: company_name, country, the registration
number, lei, period_end, currency, revenue, gross_profit, operating_profit,
profit_before_tax, net_income, total_assets, current_assets, cash_and_equivalents,
total_equity, net_assets, total_liabilities, employees, metrics_found and the source links
(report_url, registry_url, source_url). A missing figure was not filed; never treat it as
zero.

Cost to the user: $0.04 per company-year returned.

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_company_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNoMax company-years per country to return (1-10).
dk_cvr_numbersNoDanish 8-digit CVR numbers, e.g. 24256790
no_org_numbersNoNorwegian 9-digit org numbers, e.g. 923609016
uk_company_numbersNoCompanies House numbers, e.g. 03117531

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 the annotations (readOnlyHint, openWorldHint), the description discloses substantive behavior: per-country coverage limits (UK only digitally filed iXBRL years, DK all years, NO the last 3 fiscal years own-vs-group), ordering (newest fiscal year first), the pricing model ($0.04 per company-year), and the crucial caveat that a missing figure means it was not filed and must not be read as zero.

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?

The text is front-loaded with purpose, followed by a labelled 'Coverage:' block, a constraint line, an output description and a cost note — easy to scan. The long field enumeration for the return row is partly redundant given an output schema exists, so the prose runs a little longer than necessary.

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?

For a multi-registry financial lookup with a rich output schema, the description covers scope, coverage gaps, ordering, the missing-value interpretation rule and cost — everything an agent needs before invoking it. The redundant field list is harmless, and the pricing/coverage caveats are the kinds of detail only the description can supply.

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 100% so the per-parameter formats are already documented, and the description adds a constraint the schema does not encode: 'Pass at least one registration number', which is essential because the schema marks zero required parameters. The note on row granularity (one row per company per fiscal year, newest first) also clarifies what max_results actually counts.

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 definition names a specific resource (company accounts/financials), the exact jurisdictions (UK, DK, NO) and the underlying registries, so an agent can immediately tell it apart from SEC-oriented siblings like find_sec_company or get_eu_annual_reports. It also states the trigger (you know the registration number) and the fields served (revenue, profit, equity, cash, employees).

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 a clear when-to-use rule: for private/company financials in these three countries when a registration number is known. It does not name a specific alternative to use for other countries (US/EU siblings exist), but the country scoping implicitly routes the agent away from them, so this is strong context without explicit exclusions.

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