Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_uk_france_tenders

Read-onlyIdempotent

Search UK Contracts Finder and France BOAMP public procurement tenders and contract awards by keyword, with buyer contacts, CPV codes, deadlines, GBP/EUR values, and awarded suppliers.

Instructions

Query UK Contracts Finder (OCDS) and France BOAMP government procurement tenders and contract awards with buyer contact emails, CPV codes, deadlines, GBP/EUR values, and awarded suppliers (corridordata/uk-france-public-tenders-ocds).

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": "search_uk_france_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNoEnglish or French sector keywords (e.g. ['software', 'logiciel', 'cloud', 'cyber']).
maxItemsNoMaximum UK/French procurement notices to return.
countriesNoPortals to query: UK (Contracts Finder), FR (BOAMP), or both.
recordModeNoFilter open tenders, awarded contracts, or all notices.open_tenders
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds the returned content set and names the underlying dataset, but says nothing about pagination, result ordering, latency, or billing behavior beyond what the schema's maxTotalChargeUsd parameter already implies.

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?

A single front-loaded sentence with no filler, though it is dense with a parenthetical standard name and dataset slug. Every element earns its place as scoping information, but the packing makes it slightly harder to parse at a glance than two shorter clauses would be.

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?

With no output schema, the description usefully enumerates what comes back, and all five parameters are optional, lowering the cost of a wrong call. It stops short of covering result volume, pagination, or how keywords interact across the two portals' different languages.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameter documentation is already handled by the schema; the description adds little parameter-level meaning but doesn't need to. The enumerated fields loosely correspond to filtering dimensions (CPV codes, countries, deadlines), which is consistent rather than contradictory.

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?

Names specific sources (UK Contracts Finder/OCDS, France BOAMP), the resource type (tenders and contract awards), and the concrete fields returned (contact emails, CPV codes, deadlines, GBP/EUR values, awarded suppliers). This clearly separates it from siblings like search_global_tenders and search_spain_public_tenders without needing to open the schema.

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 geographic and data scope imply when the tool applies, but there is no explicit when-to-use or when-not guidance, no mention of when to prefer search_global_tenders or a country-specific sibling, and no prerequisites or exclusions. Usage must be inferred from the described coverage.

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