tendfeed-mcp

Official

Overview Schema Source Related Servers Discussions Admin

search_tenders

Read-only

Search EU public tenders and get a bid/no-bid verdict with competition density, price corridor, SME fit, and deadline. Filter by sector, country, SME-only, and minimum score.

Instructions

Open EU tenders with a bid/no-bid verdict (Worth-It score, reason, competition density, price corridor where robust, deadline, SME-fit). Filter by sector (CPV division), country (NUTS), SME-only, min score. Guests (no key) get the expired-tender board plus a live_matched count; an API key (Authorization: Bearer cfm_live_…) with an active TendFeed subscription unlocks the live, still-biddable board. Data/research tool over TED (Tenders Electronic Daily, CC BY 4.0). No guarantee of award.

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_tenders"
  }
}

Input Schema

Name	Required	Description
`cpv`	No	CPV division prefix, e.g. 45 (construction), 72 (IT), 33 (medical)
`nuts`	No	Country prefix, e.g. DE, FR, PL
`limit`	No
`sme_only`	No
`min_score`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds context about the data source (TED, CC BY 4.0), authentication tiers (guest vs. API key), and a disclaimer about no guarantee of award. This goes beyond what annotations provide, but does not cover rate limits or pagination.

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 a single paragraph but packs essential information: purpose, output fields, filters, authentication, and data source. It could be improved by breaking into bullet points for readability, but it is not overly verbose.

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?

Given the absence of an output schema, the description reasonably explains what the tool returns (list of tenders with verdict details) and covers authentication differences. However, it omits pagination details and does not mention ordering or other common search parameters, leaving some gaps.

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 includes descriptions for all 5 parameters, so baseline is 3. The description echoes these filters (sector, country, SME-only, min score) without adding new semantics or usage details for each parameter, so it does not significantly enhance understanding.

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 it searches open EU tenders with a bid/no-bid verdict, listing specific output fields like Worth-It score, reason, competition density etc. This distinguishes it from sibling tools like find_winnable_lanes or get_verdict which have different scopes.

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 description explains the tool's purpose and notes that guests get expired tenders while API key holders get live ones, but it does not explicitly contrast with sibling tools or specify when not to use this tool. The usage context is implied but not fully directed.

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

Deploy Server