Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Belgian annual accounts (NBB)

get_belgian_company_filing
Read-only

Retrieves a Belgian company's official annual-account filing as a base64-encoded PDF. Use it to obtain filed financial statements from a deposit reference returned by the filings list.

Instructions

One Belgian annual-account deposit as filed (NBB CBSO Authentic Data): Belgian company financial statements as the official PDF, returned base64-encoded. Reference comes from list_belgian_company_filings. Deposits are immutable. A sole proprietorship or a legal form in doubt in the KBO copy is refused (404, not charged), like an enterprise number the KBO copy does not hold or whose name is under objection (the profile's 404); an empty KBO copy answers 503 collecte_en_cours. The structured JSON-XBRL, when the NBB publishes one, is on the REST route with ?format=json (sorted: directors and shareholders removed and counted). Paid via x402 ($0.15 in USDC or EURC).

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": {
      "id": "<id>",
      "reference": "<reference>"
    },
    "name": "get_belgian_company_filing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes10-digit Belgian enterprise number (KBO/BCE)
referenceYesDeposit reference taken from the filings list, e.g. 2026-00123205

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses immutability of deposits, the exact refusal conditions (sole proprietorship or doubtful legal form → 404, not charged; unknown enterprise number or name under objection → 404; empty KBO copy → 503 collecte_en_cours), the payment mechanism and price (x402, $0.15 USDC/EURC), and the base64 return encoding. This is unusually rich behavioral context for a read tool.

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 purpose and return format are front-loaded and no sentence is filler, but the middle section is a single dense run of parenthetical asides (error codes, KBO copy conditions) that takes effort to parse. Slight restructuring into short sentences would improve it without losing content.

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 two-parameter read-only fetch with no output schema, the description covers what is returned (base64 PDF), what the structured alternative is, what failure modes mean and cost, and how payment works. Nothing an agent needs to invoke it correctly 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 coverage is 100%, with both id (10-digit KBO/BCE number) and reference (deposit reference) documented with patterns, so the schema carries most of the burden. The description adds provenance for reference ('comes from list_belgian_company_filings') and ties the id to KBO copy error behavior, but adds little about format beyond the schema.

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 nominal phrasing identifies exactly one resource: a single Belgian annual-account deposit as filed with the NBB, returned as a base64 PDF. It distinguishes itself from the sibling list tool by stating the reference must come from list_belgian_company_filings, and from the JSON variant by naming the REST route with ?format=json.

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 clearly tells the agent where the required reference comes from (the filings list) and points to the alternative route when structured JSON-XBRL is wanted instead of the PDF. It stops short of an explicit 'do not call without first listing' instruction or a stated precondition ordering, so guidance is strong but not fully prescriptive.

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

Deploy Server

Other Tools