Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company briefing for an AI

get_french_company_briefing
Read-only

Generate an LLM-ready Markdown briefing for a French company from its SIREN, covering identity, filed accounts, insolvency notices, court decisions, and public contracts.

Instructions

LLM-ready briefing on a French company (SIREN), returned as Markdown text to read or paste as is: identity without officers, filed accounts over three years with their reliability, BODACC insolvency notices, commercial-court decisions and public contracts counted and dated, each block with its status, age and coverage. Written by code from official registers, no model text; legal entities only (a sole proprietorship answers 400, never charged). The text opens with its instruction and ends with its source line: copy it verbatim. Paid via x402 ($0.05 in USDC or EURC).

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": {
      "siren": "<siren>"
    },
    "name": "get_french_company_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN
langueNofr or en; default: the API key account's language, else fr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that each block carries status, age and coverage, that the text is code-generated from official registers with no model text, that the text opens with an instruction and ends with a source line meant to be copied verbatim, and that access is paid via x402 in USDC or EURC. That is exactly the kind of behavioral and cost context annotations cannot convey.

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 what the tool returns and its format, then layered with content inventory, provenance, eligibility and pricing. Dense but every clause carries information; the pricing sentence at the end could arguably be its own short line for scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-format burden and does so well: Markdown, per-block status/age/coverage, embedded instruction and source line. Error behavior beyond the sole-proprietorship 400 and any rate/coverage limits are the remaining gaps, but overall it is sufficient to call the tool correctly.

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 both parameters (siren pattern, langue enum with default fallback to the account language) are fully documented in the schema. The description confirms SIREN as the company key but adds nothing about the language parameter or how output language interacts with the generated text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (French company, keyed by SIREN) and a concrete output form (LLM-ready Markdown briefing) and enumerates what the briefing contains (identity without officers, three years of accounts with reliability, BODACC insolvency notices, court decisions, public contracts). This content enumeration implicitly separates it from the many single-domain siblings, though no sibling is named as an alternative.

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?

Gives real usage constraints: legal entities only (a sole proprietorship returns HTTP 400 and is never charged) and a $0.05 x402 charge, plus the instruction to copy the output verbatim. It never says when to pick this composite briefing over the narrower siblings such as get_french_company_financials or get_french_company_court_decisions, so routing 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