Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Public Procurement Trends

procurement_fr_trends

Builds monthly or yearly time series of awarded French public-contract volumes and amounts from DECP. Use when: Track how French awarded public-contract volumes and amounts evolve month by month or year by year. Avoid when: Use procurement/fr/market for a current segment overview without a time series. Use procurement/fr/search for open tender opportunities. Limitations: The current partial month or year can mechanically reduce the latest period. Price: 0.020 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
NameRequiredDescriptionDefault
buyerNoPublic-buyer name or identifier used to restrict procurement results. (minimum length 2; maximum length 200).
cpv_prefixNoOptional CPV prefix used to restrict procurement records to a purchasing segment.
departmentNoOptional French department code used to restrict results geographically.
granularityNoOptional value for “granularity” as defined by this API contract. (default month; allowed values: month, year).month
lookback_monthsNoOptional value for “lookback months” as defined by this API contract. (minimum 1; maximum 60; default 24).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
seriesYesStructured value returned for “series” as defined by this API contract.
filtersYesStructured value returned for “filters” as defined by this API contract.
granularityYesStructured value returned for “granularity” as defined by this API contract. (allowed values: month, year).
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
generated_atYesUTC timestamp at which this derived result was generated.
periods_countYesStructured value returned for “periods count” as defined by this API contract.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok, unavailable).
lookback_monthsYesStructured value returned for “lookback months” as defined by this API contract.
latest_period_contracts_change_percentYesStructured value returned for “latest period contracts change percent” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "filters",
-  "lookback_months",
-  "granularity",
-  "source_status",
-  "periods_count",
-  "latest_period_contracts_change_percent",
-  "series",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "filters",
+  "lookback_months",
+  "granularity",
+  "source_status",
+  "periods_count",
+  "latest_period_contracts_change_percent",
+  "series",
+  "generated_at"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing that source records are not modified, that a successful paid invocation can consume the x402 payment, that the payment challenge itself is free, and that the current partial period can mechanically reduce the latest data point. These are meaningful behavioral caveats an agent needs to interpret results and predict side effects.

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?

The description is well organized with clear sections, front-loads the core behavior, and keeps the payment and network details relevant. It earns a minor deduction because the main sentence and the 'Use when' sentence duplicate nearly the same idea, making the opening slightly redundant.

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, all five parameters are fully documented in the schema, and annotations are present, the description is complete. It adds the missing non-schema context: usage scenarios, alternatives, a data caveat, pricing, payment behavior, and accepted networks.

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%, so the baseline is 3. The description does not add new meaning to the parameters themselves; it only states the general data source and time-series nature, while the schema already documents buyer, cpv_prefix, department, granularity, and lookback_months with constraints and defaults.

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 specific verb ('Builds') and a precise resource ('monthly or yearly time series of awarded French public-contract volumes and amounts from DECP'). It distinguishes itself from related procurement tools by explicitly naming what it is not (market overview, open tender search), so an agent can select it confidently.

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 'Use when' clause gives the exact scenario for this tool, and the 'Avoid when' clause names two alternatives with the conditions that make them more appropriate. This leaves no ambiguity about when to choose this tool versus its siblings.

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

All HelpMyAgent 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