Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

German insider transactions

get_german_insider_transactions
Read-only

Query German listed-company insider transactions by LEI or ISIN to see manager buying/selling: rolling 12-month notification counts, gross buy/sell amounts, net flow, and declarer-category breakdown.

Instructions

Insider transactions at a German listed company (directors' dealings under MAR Article 19, as notified to BaFin): 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. Query by LEI or ISIN (BaFin publishes no company register number). No individual is ever named, and the breakdown is withheld when it would single someone out. 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_german_insider_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLEI (20 chars, ISO 17442) or ISIN (12 chars) of the German listed issuer
depuisNoStart date YYYY-MM-DD (default: rolling 12 months; BaFin keeps 12 months; never earlier than five years back, 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.6/5.0
Behavior5/5

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

Far exceeds the annotations (readOnlyHint, openWorldHint): it discloses a paid x402 call at $0.02 in USDC or EURC, a privacy rule that no individual is ever named and breakdowns are withheld when they would single someone out, and a mandatory verbatim `citation` in reporting. It also flags the data window (BaFin keeps 12 months), all of which materially shape how an agent should call and report the result.

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-loads the core question and scope before the logistics, and every clause carries information (identifiers, privacy, payment, citation). It is dense and parenthetical, reading as one long accumulation rather than cleanly separated sections, which costs a point but no sentence is filler.

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 an output schema already exists, the description covers everything else an agent needs: identifier choice, default time window, privacy limits on the output, payment requirement, and the citation obligation. Nothing required to call it correctly or report it responsibly is missing.

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 baseline is 3, but the description adds rationale the schema lacks: why only LEI or ISIN is accepted (no BaFin company register number). The rolling-12-month default and date bounds are already covered by the `depuis` schema description, so the added value is modest rather than exhaustive.

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 — insider transactions (directors' dealings under MAR Article 19 notified to BaFin) at a German listed issuer — plus the exact scope of the answer: issuer-level aggregate over a rolling 12 months with counts, gross buy/sell amounts, net flow, declarer breakdown and underlying notifications. The framing question ('are its managers buying or selling?') makes the resource instantly distinguishable from the Belgian and other country 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 clear use context and the key identifier constraint ('Query by LEI or ISIN (BaFin publishes no company register number)'), which steers the agent away from trying a registration number. It does not, however, name any alternative tool or state when-not-to-use conditions, so routing beyond country scope 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.

Deploy Server

Other Tools