Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French procurement competitors

get_company_procurement_competitors
Read-only

Identify rival contractors winning French public contracts on the same CPV segments as a given SIREN, with 3-year counts, amounts, and shared segments from official DECP data.

Instructions

Competitive intelligence on French public procurement: who wins contracts on the SAME CPV segments as a given company (SIREN): top rival contractors over the last 3 years with counts, amounts and shared segments. From official DECP open data. Paid via x402 ($0.02 in USDC or EURC). Names are served for legal persons proven by their Sirene legal category only: a sole proprietorship, a group of natural persons or a category in doubt never has its name served and keeps its SIREN or SIRET, the omissions counted without identity in ecartes, over the entries the response serves (rule R1). 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": {
      "siren": "<siren>"
    },
    "name": "get_company_procurement_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN

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?

With only readOnlyHint and openWorldHint supplied, the description adds substantial context: the official DECP data source, the $0.02 x402 payment in USDC or EURC, and the legal-person naming rule R1 where sole proprietorships or uncertain categories keep their SIREN/SIRET with omissions counted in 'ecartes'. It also instructs that the returned `citation` be reproduced verbatim, which materially affects how an agent reports results.

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 the core value proposition, then cost, then the legal naming caveat and citation rule. Each sentence carries information, though the R1 naming sentence is dense and run-on, slowing parsing of an otherwise tight definition.

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?

An output schema exists, so return values need not be enumerated, yet the description still previews the payload (counts, amounts, shared segments, ecartes) and covers billing, source provenance, and citation obligations. Nothing an agent needs to invoke or report this tool 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?

Only one parameter exists and the schema already documents it fully at 100% coverage ('9-digit SIREN' with a ^\d{9}$ pattern). The description restates that the input is a SIREN for a company but adds no format, normalization, or error-handling 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 resource and analytic scope: 'who wins contracts on the SAME CPV segments as a given company (SIREN): top rival contractors over the last 3 years with counts, amounts and shared segments.' That clearly separates it from the sibling get_french_company_public_procurement, which returns the company's own awards rather than rivals'.

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?

The scope ('SAME CPV segments', 'last 3 years') implies when the tool is appropriate, but there is no explicit when-to-use statement, no exclusion of alternatives such as the own-awards procurement tool, and no note on prerequisites beyond the SIREN requirement.

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