Sirenic

Belgian filings list (NBB)

list_belgian_company_filings

Read-only

Belgian company annual accounts — list every published deposit of a Belgian company at the NBB CBSO (Central Balance Sheet Office, Authentic Data): deposit references with filing metadata as published. Unique on x402: no other service exposes Belgian filed accounts. Paid via x402 ($0.01 in USDC or EURC).

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	10-digit Belgian enterprise number (KBO/BCE), e.g. 0403170701
`api_key`	No	Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402 — no wallet needed. Get one at https://api.sirenic.eu/compte. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.
`x_payment`	No	Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	How to settle the quote, present when payment_required is true.
`quote`	No	The signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
`resultat`	No	The endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature; KYB, batch KYB, sanctions, intelligence and the five invoicing tools (prepare_french_invoice_file, prepare_european_invoice_file, prepare_french_einvoicing_recipient, verify_iban_bank, validate_eu_vat_number) also carry a `provenance` array — one entry per block served, with the official register, licence, version, `as_of` date and `precision_as_of` (what that date means). Codes are documented at GET /v1/provenance/registres (free).
`payment_required`	Yes	True when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already signal read-only and open-world behavior, and the description adds useful context: results are 'as published' (no normalization), the source is the CBSO Authentic Data, and the call is paid via x402 at a stated price. This goes beyond annotations without contradicting them.

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?

The description is two tight sentences with the core scope front-loaded and no filler. The uniqueness and pricing statements earn their place because they affect tool selection and invocation expectations.

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?

Given the required enterprise number is fully explained in the schema, payment options are documented, and an output schema is present, the agent has what it needs to decide and invoke the tool. The description supplies the missing invocation context: source, scope, exclusivity, and cost.

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?

All three parameters are fully documented in the schema (100% coverage), including the 10-digit enterprise-number pattern, the api_key alternative, and the x_payment omission behavior. The description's payment line adds no parameter-level meaning beyond what the schema already provides.

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 description opens with 'Belgian company annual accounts' and then states a precise action and target: 'list every published deposit of a Belgian company at the NBB CBSO.' It also defines the output as 'deposit references with filing metadata as published' and explicitly claims no other x402 service exposes Belgian filed accounts, making it easy to distinguish from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when this tool is relevant—Belgian NBB CBSO deposits—and claims uniqueness, which helps route an agent toward it for Belgian accounts. However, it does not explicitly contrast itself with the sibling get_belgian_company_filing, so when to list all deposits versus retrieve a single filing is left to inference.

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

All Sirenic tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Several French company bundles overlap in purpose (get_french_company_file, get_french_company_kyb_file, get_french_company_intelligence, get_french_company_health_summary) and procurement/competitor tools overlap (get_french_company_public_procurement, get_eu_procurement_awards, get_company_procurement_competitors). Although descriptions try to differentiate, an agent could easily select the wrong tool when looking for a company overview or procurement history.

Naming Consistency4/5

Most tools follow a consistent get_/list_/search_ + country + entity pattern, e.g. get_french_company_profile, list_danish_company_filings, so navigation is predictable. Deviations like check_french_regulator_alerts, suggest_company_names, verify_iban_bank, and the prepare_* verbs are understandable but break the strict verb_noun pattern.

Tool Count1/5

77 tools is excessive for a single server regardless of how broad the domain is; the calibration treats 50+ as an extreme mismatch. While France is well covered and several countries appear, much of the surface is micro-endpoints (list_/get_ filing pairs per country) that could be consolidated.

Completeness3/5

France coverage is impressively complete (identity, financials, legal events, procurement, IP, risk, surveillance, invoicing), and the surveillance lifecycle has create/get/renew/stop. But European coverage is inconsistent: Germany has only insider transactions, Spain only acts, and several major jurisdictions lack accounts/officers/insolvency; an agent expecting 'European company due diligence' will hit dead ends.

Resources

Need Help?