Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Belgian insider transactions

get_belgian_insider_transactions
Read-only

Retrieve FSMA-notified insider buying and selling aggregates for a Belgian listed company to assess governance risk before investing or contracting.

Instructions

Insider transactions at a Belgian listed company (managers transactions under MAR Article 19, as notified to the FSMA): are its managers buying or selling? Issuer-level aggregate over a rolling 12 months: notification counts, gross buy and sell amounts, net flow, breakdown by declarer category, plus the underlying notifications. No individual is ever named, and the breakdown is withheld when it would single someone out. A day of the window that the FSMA listing could not return whole is named in collecte_incomplete (counts are then lower bounds). Use it as a governance signal before investing in or contracting with a listed Belgian company. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

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>"
    },
    "name": "get_belgian_insider_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes10-digit Belgian enterprise number (KBO/BCE)
depuisNoStart date YYYY-MM-DD (default: rolling 12 months; never earlier than five years back: older notifications are deleted, and periode.depuis_demande says when a request was bounded)

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe 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`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue 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`.

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, it discloses privacy behavior (no individual ever named, breakdown withheld when it would single someone out), data-quality limits (incomplete FSMA days surfaced in collecte_incomplete, counts become lower bounds), the five-year retention horizon, and the x402 payment cost. These are exactly the operational facts an agent cannot get from structured fields.

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 the core question ('are its managers buying or selling?') followed by scope, privacy rules, caveats, and usage. Dense but every sentence carries information; the parenthetical MAR/FSMA clause and the citation instruction are slightly heavy but justified.

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, single-issuer read tool with an output schema and read-only annotations, the description covers scope, window defaults, privacy and truncation caveats, cost, and citation requirements. Nothing an agent needs to decide or call 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 description coverage is 100%, so `id` (10-digit KBO/BCE) and `depuis` (YYYY-MM-DD, default rolling 12 months, five-year floor) are already fully documented in the schema. The description restates the rolling-12-month default and the five-year bound without adding calling syntax, so the baseline of 3 applies.

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+resource: manager transactions under MAR Article 19 at a Belgian listed company, aggregated at issuer level over a rolling 12 months, with enumerated outputs (counts, gross buy/sell, net flow, declarer breakdown, underlying notifications). The country scope in the name plus the MAR/FSMA framing clearly separates it from the German sibling.

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 an explicit situation for use: a governance signal before investing in or contracting with a listed Belgian company. It does not name an alternative tool or state when-not to use it (e.g., for non-listed entities or for single-notification lookups), so it stops short of full routing guidance.

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