Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French association profile (RNA)

get_french_association_profile
Read-only

Retrieve the official profile of a French association by its RNA number, including status, purpose codes, and registered office—ideal for verifying associations without a SIREN.

Instructions

Official profile of a French association (loi 1901) by RNA number from the Répertoire national des associations (Ministry of the Interior, monthly export): title, purpose and Waldec purpose codes, nature and grouping, position (active/dissolved/deleted), creation, declaration, JO publication and dissolution dates, registered office, website, RUP number as declared, prefecture, and the SIREN when Sirene confirms an association. Covers associations WITHOUT a SIREN; use search_french_associations first when you only have a name. No officer or declarant data; Alsace-Moselle excluded (local law). Unknown identifier = 404, not charged. Paid via x402 ($0.005 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rnaYesRNA number (W + 9 characters, e.g. W751004076) or legacy RNA identifier as published (3-14 characters)

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?

Annotations only declare readOnly and openWorld, but the description adds material behavior: unknown identifier returns 404 and is not charged, the result is a paid x402 call at $0.005 in USDC or EURC, data freshness is a monthly export, and results must be cited verbatim from a `citation` field. These are cost, error and compliance traits an agent cannot infer 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?

Identity and source are front-loaded, and the trailing sentences each carry a distinct operational fact (scope, exclusions, error/pricing, citation). The long field-enumeration clause is dense but earns its place by signaling what the profile returns; a slightly tighter list would read better.

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 lookup with an output schema, the description need not explain return values, yet it still covers source, freshness, coverage gaps, exclusions, error behavior, pricing and citation obligations. Nothing an agent needs to call 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% and the single `rna` parameter already documents the W+9 format and the 3-14 character legacy form, so the description adds no syntax detail beyond it. Baseline 3 applies when the schema carries the parameter semantics.

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 ('Official profile of a French association (loi 1901) by RNA number') and names the authoritative source registry. The field enumeration plus the explicit scope 'Covers associations WITHOUT a SIREN' lets an agent distinguish it from get_french_company_profile and its other siblings without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'use search_french_associations first when you only have a name.' It also states the coverage boundary (associations without SIREN) and two hard exclusions (no officer/declarant data, Alsace-Moselle excluded under local law), which is exactly the when-not guidance an agent needs.

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