Skip to main content
Glama
jocks-studio

vergabe-mcp

by jocks-studio

Search German public tenders

search_tenders
Read-only

Search active German public tenders by CPV code, location, keyword, estimated value, and deadline.

Instructions

Searches lots on oeffentlichevergabe.de. Defaults to open lots of the competition notice types (cn-standard, cn-social, cn-desg, subco, qu-sy, pin-cfc-standard, pin-cfc-social), newest first. Use search_tenders_raw for anything this does not cover.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpvNoCPV code prefixes, OR-ed, e.g. ['72', '7921'].
nutsNoNUTS codes of the place of performance.
pageNo
sortNopublicationDate
textNoFree-text query across the whole notice (allFreeText).
maxValueNoEstimated value in EUR. Set on roughly 8.5% of lots.
minValueNoEstimated value in EUR. Set on roughly 8.5% of lots.
pageSizeNo
platformNoContracting platform host, e.g. 'evergabe-online.de'.
textModeNoHow `text` is matched: all words, any word, or substring.all
onlyActiveNoRestrict to lots that are still open.
noticeTypesNoeForms notice types; defaults to the competition set (cn-standard, qu-sy, …).
suitableForNoBT-726 business types the buyer marked the lot suitable for.
deadlineAfterNoISO date or datetime; keeps lots whose first deadline is later.
sortDirectionNoDESC
contractNatureNo
publishedSinceNoISO date or datetime, inclusive lower bound.
publishedBeforeNoISO date or datetime, inclusive upper bound.
deadlineAtLeastDaysAwayNoKeep lots whose first deadline is at least N days out — bidding runway.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
totalYes
resultsYes
pageSizeYes
Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. Description adds default filtering and sorting behavior, as well as the specific website. No contradictions. Adds useful context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with core action and defaults. Second sentence provides key alternative. No wasted words.

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 19 optional parameters, an output schema that documents return values, and a sibling tool reference, the description is sufficiently complete. It covers the tool's purpose, defaults, and when to use an alternative.

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 74%, so the schema already documents most parameters. The description mentions defaults for onlyActive, noticeTypes, and sort, but these are already in the schema. No new parameter semantics beyond what schema provides.

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?

Specifically states it searches lots on oeffentlichevergabe.de with defaults (open lots, competition notice types, newest first). Clearly distinguishes from sibling search_tenders_raw by saying 'use for anything this does not cover'.

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?

Explicitly provides default behavior and references an alternative tool for cases not covered. This gives clear when-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jocks-studio/vergabe-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server