Skip to main content
Glama

Sirenic

by eu.sirenic
OverviewDiscussionsAdmin

French default risk score, batch (2 to 100)

get_french_company_default_risk_batch
Read-only

Use when asked to rank customers or suppliers by default risk, e.g. "Rank my customers by risk and monitor the 30 most exposed." Batch default-risk score for 2 to 100 French companies in one call: each line carries the SAME score, class, confidence and model version as get_french_company_default_risk (one scorecard), in a closed-list basket: expose, a_surveiller, sain, non_evaluable (with its cause), cessee (a ceased company always goes there, whatever its class). Lines are ordered by basket, then by exact axis set (jeu_axes, index into jeux_axes: two scores computed on different axes are never ranked against each other), then by score; motifs_principaux names the at most three scorecard axes that weigh most; a line whose reference year is not exploitable carries qualite_exercice_reference (fiabilite, anomalies): read it before the score. The head counts the non_evaluable lines per cause (non_evaluable_par_cause). An unknown SIREN is a billed line (trouve=false, cause siren_inconnu), and so is one whose identity is incomplete (cause identite_incomplete, with champs_absents and fiche); no line scored at all: 404, not charged, lignes naming each cause (error identite_incomplete when every SIREN is incomplete); BODACC down: the whole batch is cancelled (503), not charged. No officer, no free text; the name only for a legal entity. Statistical indicator about the company, not a decision or an assessment about a person. chainage.surveillance lists the WHOLE expose basket in served order (axis set, then score; 100 at most, never a ceased company) with the 30-day quote of create_surveillance_watch for that list: $0.05 per target x targets. To monitor the first N only, pass its first N SIRENs to create_surveillance_watch (quoted N x $0.05): a separate watch, paid on its own, checked daily, never real time. A batch holding such a SIREN (sole proprietorship, restricted diffusion, group without legal personality) is refused whole: 400, never charged, sirens_refuses gives each refused SIREN and its code; replay without them. Paid via x402 ($0.07 per SIREN in USDC or EURC, 30% off the unit score). Closed lists and reading rules: GET /v1/lecture (free). A full-size request quotes up to $7.00, above the $1.00 single-payment cap that x402 clients apply BY DEFAULT since @x402/core 2.23 (spendControls): raise spendControls.maxAmountPerPayment, or set spendControls: false, before signing; otherwise your own client rejects the quote without ever calling us. When you report a result, cite its citation verbatim.

Input Schema

NameRequiredDescriptionDefault
sirensYesList of 2 to 100 nine-digit SIRENs (deduplicated; billed per SIREN)
api_keyNoOptional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=api&utm_campaign=mcp. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.
x_paymentNoOptional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.

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. Changed1 schema field changed
    • changedOutput schema / properties / resultat / description
      Previous value: -"The 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)."New value: +"The 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)."
  2. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / free_tier / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / quote / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / resultat / propertyNames
      Added value: +{
+  "type": "string"
+}
  3. Changed7 schema fields changed
    • addedInput schema / properties / api_key
      Added value: +{
+  "description": "Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=api&utm_campaign=mcp. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.",
+  "type": "string"
+}
    • addedInput schema / properties / x_payment
      Added value: +{
+  "description": "Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.",
+  "type": "string"
+}
    • addedOutput schema / properties / free_tier
      Added value: +{
+  "additionalProperties": {},
+  "description": "Free API key offer for this tool, present with a quote.",
+  "type": "object"
+}
    • addedOutput schema / properties / hint
      Added value: +{
+  "description": "How to settle the quote, present when payment_required is true.",
+  "type": "string"
+}
    • changedOutput schema / properties / payment_required / description
      Previous value: -"Always false on this connector: every call is billed to the connected Sirenic account, never paid by the client."New value: +"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`."
    • addedOutput schema / properties / quote
      Added value: +{
+  "additionalProperties": {},
+  "description": "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`.",
+  "type": "object"
+}
    • changedOutput schema / properties / resultat / description
      Previous value: -"The 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)."New value: +"The 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)."
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: discloses per-SIREN billing ($0.07, 30% off unit), which failure modes are charged vs not (unknown SIREN billed as trouve=false; 404 uncharged; 503 BODACC-down batch cancelled; 400 refusal uncharged with sirens_refuses), the default $1.00 x402 spendControls cap that will reject a $7.00 quote, and the ordering/basket semantics of results. No contradiction with the read-only annotation — it scores, it does not mutate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, which is good, but the body is a single sprawling block of semicolon-chained clauses mixing output-field semantics (motifs_principaux, qualite_exercice_reference), error codes, pricing, and x402 client-version configuration. Most content earns its place, but the compression into run-ons hurts scannability for an agent.

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?

Output schema exists, so return fields needn't be enumerated, yet the description still explains basket ordering, chainage.surveillance contents, and every error path (404, 400 with sirens_refuses, 503) plus payment mechanics. Nothing an agent needs to call this correctly or interpret the quote 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% and all three parameters (sirens, api_key, x_payment) are already documented in the schema, including dedup and per-SIREN billing. The description reinforces billed-line and refusal behavior but adds little parameter-level detail beyond what the schema states; baseline 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 and resource (batch default-risk score for 2 to 100 French companies) and scopes it precisely against the single-company sibling by asserting 'each line carries the SAME score, class, confidence and model version as get_french_company_default_risk'. An agent can immediately tell this apart from the single-score and watch tools.

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?

Opens with an explicit trigger ('Use when asked to rank customers or suppliers by default risk') plus a concrete example, and routes to alternatives: create_surveillance_watch for monitoring a subset (with quoted pricing for first N vs whole expose basket), and the single-score tool implicitly by comparison. When-to-use and when-to-use-something-else are both covered.

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

All Sirenic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources