Skip to main content
Glama

search_german_public_tenders

Search official German public procurement tenders by city, state, keywords, and service type; retrieve deadlines, CPV codes, and documents.

Instructions

Search official German public procurement tenders (Ausschreibungen) on service.bund.de.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or 5-digit postal code of performance, e.g. 'München'.
statesNoFilter by German federal states (e.g. ['Bayern', 'Berlin']) or ['ALL'].
keywordsNoSearch keywords or topics, e.g. ['Software', 'Cloud', 'KI'].
max_itemsNoMaximum number of tender notices to retrieve (1-5000).
service_typeNoOfficial German procurement category (Leistungsart).ALL
include_detailsNoRetrieve deadlines, CPV codes, full descriptions, and document URLs.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says almost nothing: it does not state that this is a read-only lookup, whether any credentials are needed, how results are paginated, or how include_details affects result size and latency. Naming the authoritative source (service.bund.de) is the one piece of useful context added.

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 zero filler and the key entity (German public tenders) placed early. It is efficient, though the terseness leaves the definition under-informative rather than over-written.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter search tool with no annotations, one sentence is not enough: usage steering and behavioral context (read-only nature, result behavior, the effect of include_details) are absent. The existing output schema excuses it from explaining return values, which keeps this from scoring lower.

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%, with each of the six parameters documented including the service_type enum and the max_items range, so the schema does the heavy lifting and a baseline 3 applies. The description itself adds no parameter meaning beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search), a specific resource (official German public procurement tenders/Ausschreibungen), and names the source platform service.bund.de. That source detail clearly separates it from siblings like check_german_company_kyb or search_german_zvg_foreclosures, though the description never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no named alternatives. The agent can only infer applicability from the resource name; nothing tells it when this tool is the wrong choice versus the other German-data siblings.

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