Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Expiring French public contracts

find_expiring_french_public_contracts
Read-only

Surface French public contracts expiring within a 1-24 month window before any notice is published. Filter by CPV prefix and department to find upcoming tender opportunities from official DECP data.

Instructions

Tender anticipation for France: public contracts EXPIRING within a window (1-24 months, default 12): it surfaces opportunities BEFORE any notice is published. Filter by CPV prefix (45 = construction, 9091 = cleaning) and department. Returns buyer, incumbent holders, amounts, lot number when stated, whether the amount is a firm price or an ENVELOPE (call-off orders, subsequent contracts, optional tranches), declared subcontracting, framework-agreement flag (its amount is a MAXIMUM CEILING over the duration, not spend), estimated end dates (date_fin_estimee: notification + declared duration, amended where the historical DECP regime publishes it; duree_mois is the initial duration). From official DECP open data. Paid via x402 ($0.05 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). A contract subject that names a person by a civility followed by a capital letter (M., Mme, Monsieur, Madame, Maître…) is served null, counted without identity in ecartes; the contract stays (rule R1). When you report a result, cite its citation verbatim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_expiring_french_public_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpvNoOptional CPV prefix, 2-8 digits (45 = construction works)
pageNoPage, 50 per page
departementNoOptional French department code (69, 2A, 971...)
fenetre_moisNoWindow in months, 1-24 (default 12)

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.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description goes well beyond them: x402 payment of $0.05 in USDC/EURC, DECP provenance, the meaning of the framework-agreement flag (amount is a maximum ceiling, not spend), how date_fin_estimee is derived and amended, and two redaction rules under R1 governing when names are withheld. The only omission is result-volume/pagination behaviour beyond the schema's page field.

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?

The purpose is front-loaded, but the body is a run-on chain of parentheticals, heavy capitalised emphasis (EXPIRING, ENVELOPE, MAXIMUM CEILING) and a redaction rule restated almost twice ('counted without identity in ecartes'). Much of the content earns its place, yet the packaging makes it slow to parse.

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 high-complexity contract-anticipation tool the description covers provenance, payment, field semantics that could easily be misread (ceiling vs. spend, estimated vs. initial duration), and the legal-identity redaction rules affecting what is returned. Output schema exists, so the descriptive overlap on returned fields adds semantics rather than filling a gap.

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%, with patterns, ranges and defaults already documented for all four parameters, so the schema carries the load. The description adds only marginal meaning — the CPV prefix example (9091 = cleaning) complements the schema's 45 example, and it restates the 1-24 month window and default 12.

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?

The description states a precise verb and resource — public contracts EXPIRING within a 1-24 month window, surfaced before any notice is published — and names the data source (official DECP open data). This is clearly distinct from notice-search or per-company procurement siblings, which are keyed to a company or a published notice rather than to anticipated expiry.

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

Usage Guidelines4/5

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

Usage context is explicit: tender anticipation ahead of publication, with the two narrowing filters (CPV prefix, department) and the window default spelled out. What is missing is an explicit contrast with the company-centric procurement siblings for the case where the agent already has a company in hand rather than a market segment.

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