Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French association JOAFE notices

get_french_association_notices
Read-only

Retrieve official French association notices by RNA number to verify creations, changes, dissolutions, and corrections, including issue and declaration dates.

Instructions

Official Journal notices (JOAFE, DILA) of a French association by RNA number, the association equivalent of BODACC: creations, modifications (title, purpose, registered office), dissolutions, corrections, most recent first, with issue and declaration dates, prefecture, purpose themes and the PDF file name. Carries couverture (first and last loaded issue): no notice inside that window is a fact, not a gap. Weekly issue loaded every Tuesday; a stale stock returns 503 and is not charged. Paid via x402 ($0.01 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": {
      "rna": "<rna>"
    },
    "name": "get_french_association_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
rnaYesRNA number (W + 9 characters, e.g. W011006690)

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.2/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the weekly Tuesday load cadence, that a stale stock returns 503 and is not charged, the x402 price ($0.01 USDC/EURC), and the couverture window semantics. These are exactly the operational facts an agent needs before calling a paid endpoint.

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 what the tool returns, then layers coverage semantics, freshness, pricing, and the citation requirement. Dense but each clause carries distinct information; the long opening sentence is the only mild strain.

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 single-parameter paid read tool with an output schema, the description covers the remaining gaps an agent would otherwise hit: freshness, failure mode (503, uncharged), cost, and the mandatory verbatim citation. Nothing material 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% and the single rna parameter is already documented with format and an example, so the schema does the heavy lifting. The description adds only the conceptual framing ('by RNA number'), not format or validation detail 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?

States a specific verb+resource ('Official Journal notices (JOAFE, DILA) of a French association by RNA number') and anchors it with an analogy ('the association equivalent of BODACC'), plus enumerates the notice types covered. An agent can distinguish this from get_french_association_profile without opening either schema.

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?

It gives strong interpretive guidance ('no notice inside that window is a fact, not a gap') and ordering ('most recent first'), but never states when to prefer this over the sibling profile tool or what to do when the RNA is unknown. Usage is implied rather than routed.

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