Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company EU Public Contracts

company_fr_public_contracts_eu

Searches TED notices for EU public-contract awards associated with a French company name or SIREN. Use when: Find EU public-contract notices won by a French company. You need TED public-contract award notices associated with a French company at EU procurement level. You want publication numbers, buyers, winners, CPV codes and decision dates from the supported TED search. Avoid when: You need French DECP awarded contracts for the company; use company/fr/public-contracts. You need currently open French BOAMP opportunities; use procurement/fr/search. Limitations: TED matching can rely on company name and available identifiers, so notices can be missed or require manual disambiguation. The result reflects notices returned by the TED public source and is not a complete statement of all EU business won by the company. 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
limitNoMaximum number of records returned by this call. (minimum 1; maximum 50; default 20).
identifierYesFrench company identifier: 9-digit SIREN or 14-digit SIRET.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPublicly available company, person, buyer or record name for this result.
sirenYesNormalized 9-digit French SIREN when available.
existsYesWhether the requested company or public record was found in the checked source.
noticesYesStructured value returned for “notices” as defined by this API contract.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
search_queryYesStructured value returned for “search query” as defined by this API contract.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried).
returned_countYesNumber of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "source_status",
-  "search_query",
-  "returned_count",
-  "notices",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "source_status",
+  "search_query",
+  "returned_count",
+  "notices",
+  "checked_at"
+]
  2. Changed24 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/public-contracts-eu API."
    • addedInput schema / properties / identifier / description
      Added value: +"French company identifier: 9-digit SIREN or 14-digit SIRET."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 50; default 20)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/public-contracts-eu API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / exists / description
      Added value: +"Whether the requested company or public record was found in the checked source."
    • addedOutput schema / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / notices / description
      Added value: +"Structured value returned for “notices” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / buyers / description
      Added value: +"Structured value returned for “buyers” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / cpv_codes / description
      Added value: +"Structured value returned for “cpv codes” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / decision_date / description
      Added value: +"Structured value returned for “decision date” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / notice_type / description
      Added value: +"Structured value returned for “notice type” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / publication_date / description
      Added value: +"Structured value returned for “publication date” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / publication_number / description
      Added value: +"Structured value returned for “publication number” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / title / description
      Added value: +"Structured value returned for “title” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / winner_countries / description
      Added value: +"Structured value returned for “winner countries” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / winner_identifiers / description
      Added value: +"Structured value returned for “winner identifiers” as defined by this API contract."
    • addedOutput schema / properties / notices / items / properties / winners / description
      Added value: +"Structured value returned for “winners” as defined by this API contract."
    • addedOutput schema / properties / returned_count / description
      Added value: +"Number of records included in this response."
    • addedOutput schema / properties / search_query / description
      Added value: +"Structured value returned for “search query” as defined by this API contract."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / source_status / description
      Added value: +"Availability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried)."
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations are sparse (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description carries the burden. It discloses paid-call behavior, that source records are not modified, that a successful invocation can consume payment, that the payment-required challenge is free, and that repeating after a paid call may require new payment. It also notes the result is not a complete statement of all EU business won. This is substantial behavioral context beyond the annotations.

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-structured with clear 'Use when', 'Avoid when', 'Limitations', 'Price', and 'Paid-call behavior' sections. It is longer than average but every section earns its place, especially the paid-call behavior which is critical for an agent to know. Slightly verbose but not bloated.

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?

The description covers purpose, usage, limitations, pricing, and paid-call behavior. It has an output schema, so return values are documented elsewhere. The only minor gap is the mismatch between 'company name' in the description and the numeric-only identifier pattern in the schema, which could confuse an agent. Overall, it is complete for a paid API tool.

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 schema already documents both parameters (identifier and limit). The description adds that the identifier can be a French company name or SIREN, but the schema only allows a 9-digit SIREN or 14-digit SIRET pattern. This is a slight mismatch: the description mentions 'company name' as an input, but the schema's identifier pattern only accepts numeric SIREN/SIRET. The description does not add much beyond the schema's parameter docs, so baseline 3 is appropriate.

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 ('Searches TED notices'), a specific resource ('EU public-contract awards associated with a French company name or SIREN'), and lists concrete outputs (publication numbers, buyers, winners, CPV codes, decision dates). It clearly distinguishes from siblings like company_fr_public_contracts and procurement_fr_search.

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 explicitly says 'Use when' and 'Avoid when', naming the exact alternatives (company/fr/public-contracts for French DECP contracts, procurement/fr/search for open BOAMP opportunities). It also states limitations about TED matching and manual disambiguation, giving the agent clear selection criteria.

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