HelpMyAgent

French Public Contract Expiry & Renewal Signals

procurement_fr_deadlines

Estimates upcoming public-contract end dates using DECP notification, initial duration and published duration modifications, with an explicit confidence level. Use when: Find French public contracts likely to expire or renew soon, taking published DECP duration modifications into account. Avoid when: You need open tenders rather than awarded-contract expiry signals; use procurement/fr/search. Limitations: End dates remain estimates; confidence is reduced when DECP reports a modification without a revised duration. Malformed or non-date DECP modification fields are ignored and an isolated modification identifier no longer creates a modification signal by itself. Price: 0.010 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of records returned by this call. (minimum 1; maximum 50; default 25).
`cpv_prefix`	No	Optional CPV code prefix used to restrict public-contract expiry estimates to a procurement segment.
`department`	No	Optional French department code used to restrict results geographically.
`max_months`	No	Maximum number of months from now before the estimated contract end date. (minimum 1; maximum 60; default 18).
`min_months`	No	Minimum number of months from now before the estimated contract end date. (minimum 0; maximum 60; default 0).

Output Schema

TableJSON Schema

Name	Required	Description
`contracts`	Yes	Normalized public-contract records returned by the endpoint.
`cpv_prefix`	Yes	Structured value returned for “cpv prefix” as defined by this API contract.
`department`	Yes	Structured value returned for “department” as defined by this API contract.
`max_months`	Yes	Structured value returned for “max months” as defined by this API contract.
`min_months`	Yes	Structured value returned for “min months” as defined by this API contract.
`limitations`	No	Known interpretation, source-coverage or freshness limitations for this result.
`generated_at`	Yes	UTC timestamp at which this derived result was generated.
`source_status`	Yes	Availability status of the relevant upstream public source. (allowed values: ok, unavailable).
`returned_count`	Yes	Number of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / required

Previous value: -[
-  "cpv_prefix",
-  "department",
-  "min_months",
-  "max_months",
-  "source_status",
-  "returned_count",
-  "contracts",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "cpv_prefix",
+  "department",
+  "min_months",
+  "max_months",
+  "source_status",
+  "returned_count",
+  "contracts",
+  "generated_at"
+]

Changed8 schema fields changedSep 9, 2026

addedOutput schema / properties / contracts / items / properties / duration_source

Added value: +{
+  "description": "Structured value returned for “duration source” as defined by this API contract. (allowed values: decp_initial, decp_modification).",
+  "enum": [
+    "decp_initial",
+    "decp_modification"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / contracts / items / properties / effective_duration_months

Added value: +{
+  "description": "Structured value returned for “effective duration months” as defined by this API contract.",
+  "type": "integer"
+}

addedOutput schema / properties / contracts / items / properties / estimated_end_confidence

Added value: +{
+  "description": "Structured value returned for “estimated end confidence” as defined by this API contract. (allowed values: low, medium, high).",
+  "enum": [
+    "low",
+    "medium",
+    "high"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / contracts / items / properties / modification_date

Added value: +{
+  "description": "Structured value returned for “modification date” as defined by this API contract.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / contracts / items / properties / modification_detected

Added value: +{
+  "description": "Structured value returned for “modification detected” as defined by this API contract.",
+  "type": "boolean"
+}

addedOutput schema / properties / contracts / items / properties / modification_id

Added value: +{
+  "description": "Structured value returned for “modification id” as defined by this API contract.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / contracts / items / properties / modification_object

Added value: +{
+  "description": "Structured value returned for “modification object” as defined by this API contract.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / contracts / items / required

Previous value: -[
-  "contract_id",
-  "object",
-  "cpv",
-  "buyer_siret",
-  "buyer_name",
-  "holder_sirets",
-  "amount",
-  "notification_date",
-  "duration_months",
-  "estimated_end_date",
-  "months_until_end",
-  "execution_location"
-]New value: +[
+  "contract_id",
+  "object",
+  "cpv",
+  "buyer_siret",
+  "buyer_name",
+  "holder_sirets",
+  "amount",
+  "notification_date",
+  "duration_months",
+  "effective_duration_months",
+  "duration_source",
+  "modification_detected",
+  "modification_id",
+  "modification_date",
+  "modification_object",
+  "estimated_end_date",
+  "estimated_end_confidence",
+  "months_until_end",
+  "execution_location"
+]

Changed28 schema fields changedSep 8, 2026

addedInput schema / description

Added value: +"Structured input parameters for the procurement/fr/deadlines API."

addedInput schema / properties / cpv_prefix / description

Added value: +"Optional CPV code prefix used to restrict public-contract expiry estimates to a procurement segment."

addedInput schema / properties / department / description

Added value: +"Optional French department code used to restrict results geographically."

addedInput schema / properties / limit / description

Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 50; default 25)."

addedInput schema / properties / max_months / description

Added value: +"Maximum number of months from now before the estimated contract end date. (minimum 1; maximum 60; default 18)."

addedInput schema / properties / min_months / description

Added value: +"Minimum number of months from now before the estimated contract end date. (minimum 0; maximum 60; default 0)."

addedOutput schema / description

Added value: +"Structured result returned by the procurement/fr/deadlines API."

addedOutput schema / properties / contracts / description

Added value: +"Normalized public-contract records returned by the endpoint."

addedOutput schema / properties / contracts / items / properties / amount / description

Added value: +"Structured value returned for “amount” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / buyer_name / description

Added value: +"Structured value returned for “buyer name” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / buyer_siret / description

Added value: +"Structured value returned for “buyer siret” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / contract_id / description

Added value: +"Structured value returned for “contract id” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / cpv / description

Added value: +"Structured value returned for “cpv” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / duration_months / description

Added value: +"Structured value returned for “duration months” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / estimated_end_date / description

Added value: +"Structured value returned for “estimated end date” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / execution_location / description

Added value: +"Structured value returned for “execution location” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / holder_sirets / description

Added value: +"Structured value returned for “holder sirets” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / months_until_end / description

Added value: +"Structured value returned for “months until end” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / notification_date / description

Added value: +"Structured value returned for “notification date” as defined by this API contract."

addedOutput schema / properties / contracts / items / properties / object / description

Added value: +"Structured value returned for “object” as defined by this API contract."

addedOutput schema / properties / cpv_prefix / description

Added value: +"Structured value returned for “cpv prefix” as defined by this API contract."

addedOutput schema / properties / department / description

Added value: +"Structured value returned for “department” as defined by this API contract."

addedOutput schema / properties / generated_at / description

Added value: +"UTC timestamp at which this derived result was generated."

addedOutput schema / properties / limitations / description

Added value: +"Known interpretation, source-coverage or freshness limitations for this result."

addedOutput schema / properties / max_months / description

Added value: +"Structured value returned for “max months” as defined by this API contract."

addedOutput schema / properties / min_months / description

Added value: +"Structured value returned for “min months” as defined by this API contract."

addedOutput schema / properties / returned_count / description

Added value: +"Number of records included in this response."

addedOutput schema / properties / source_status / description

Added value: +"Availability status of the relevant upstream public source. (allowed values: ok, unavailable)."

AddedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With all annotations set to false (readOnlyHint=false, etc.), the description carries the full burden of behavioral disclosure. It explicitly states that source records are not modified, but a paid invocation consumes the x402 payment, the payment-required challenge is free, and repeating the tool may require a new payment. It also discloses that end dates are estimates, confidence is reduced under certain conditions, and how malformed fields are handled. This is thorough and directly addresses the tool's side effects and reliability.

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

Conciseness5/5

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

The description is well-structured with clear sections: purpose, use/avoid, limitations, price, paid-call behavior, and accepted networks. It is front-loaded with the core purpose, then provides necessary operational details. Every sentence adds value—no redundancy. The length is justified given the need to convey estimation behavior, payment specifics, and limitations without becoming verbose.

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?

Given that an output schema exists (indicated by 'Has output schema: true'), the description does not need to explain return values. It covers all other essential aspects: purpose, usage, limitations, pricing, paid-call behavior, and network support. The description is complete for an agent to correctly decide when to use it, what to expect, and how to handle side effects. No missing critical information.

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?

The input schema already provides full descriptions for all five parameters, and the schema coverage is 100%. The tool description does not add parameter-specific semantics beyond what the schema provides; it only references the overall purpose. Since the schema handles parameter documentation adequately, a baseline of 3 is appropriate. The description's mention of 'taking published DECP duration modifications into account' is algorithm-related rather than parameter-specific.

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 clearly states the tool's function: estimating upcoming public-contract end dates using DECP notification, initial duration, and duration modifications, with an explicit confidence level. It also distinguishes itself from the sibling tool 'procurement/fr/search' by explicitly saying 'Avoid when: You need open tenders rather than awarded-contract expiry signals; use procurement/fr/search.' This gives a specific verb, resource, and differentiates it from alternatives.

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?

The description provides explicit 'Use when' and 'Avoid when' sections, directly naming the alternative tool and the condition for choosing it. It also lists limitations (confidence reduced when DECP reports a modification without a revised duration, malformed fields ignored, isolated modification identifier no longer creates a signal) which guide the agent on appropriate usage. This is comprehensive and leaves no ambiguity.

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

All HelpMyAgent tools Inspect

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

Need Help?