Diavgis — Greek Public Procurement

Search Greek Procurement Acts

search_tenders

Read-onlyIdempotent

Search Greek public-procurement acts across THREE cross-linked sources — Διαύγεια, ΚΗΜΔΗΣ (Central Electronic Public Procurement Registry) and EU TED. Filter by source (diavgeia|kimdis|ted), lifecycle status (request|tender|award|contract|payment), buyer or supplier ΑΦΜ (9-digit tax id), CPV code, EUR budget range, NUTS region, submission deadline (deadline_after=TODAY + status=tender ⇒ the OPEN tenders a supplier can still bid on), free-text q over the act title, and procurement signals (published facts from ΚΗΜΔΗΣ): direct_award (απευθείας ανάθεση), single_bidder (≤1 bid on the contract), cancelled. Returns a paginated envelope; 'next' is the next PAGE NUMBER or null. Natural-person counterparties are redacted. Do NOT sum amount_net across results to get spend — use rank_entities or spend_by_cpv, which count each procurement once.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	free-text search over the act title
`cpv`	No	CPV code (e.g. 79710000)
`page`	No	1-based page number; pagination DEPTH is capped per plan
`year`	No	4-digit issue year, e.g. 2026 — restricts to acts issued that year
`region`	No	NUTS region code prefix, e.g. EL30 (Attica), EL52 (Central Macedonia). Matches by prefix, so EL3 covers all of Attica.
`source`	No	filter by data source
`status`	No
`buyer_afm`	No	9-digit buyer ΑΦΜ
`cancelled`	No	only acts the source marked as cancelled
`has_chain`	No	only acts linked into a reconstructed lifecycle chain (request→tender→award→contract→payment)
`page_size`	No	max 200
`budget_max`	No	maximum amount_net in EUR
`budget_min`	No	minimum amount_net in EUR
`price_only`	No	only awards/contracts decided on lowest-price alone (award_criteria = Βάσει τιμής / Χαμηλότερη Τιμή), excluding most-economically-advantageous (MEAT) criteria
`direct_award`	No	only direct awards (procedure = απευθείας ανάθεση) — a published ΚΗΜΔΗΣ fact
`supplier_afm`	No	9-digit supplier ΑΦΜ
`single_bidder`	No	only contracts where ≤1 bid was submitted (maxBidsSubmitted; single bidder)
`deadline_after`	No	ISO date (YYYY-MM-DD). Only acts whose submission deadline is on/after this date. Pass TODAY to get OPEN tenders — the ones a supplier can still bid on. Combine with status="tender".

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`next`	Yes	next page NUMBER, or null when there are no more pages — not a URL
`page`	Yes
`total`	Yes	total acts matching the filters
`page_size`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / properties / data / items / properties / supplier_afm / description

Previous value: -"null when the counterparty is a redacted natural person"New value: +"9-digit ΑΦΜ of a company supplier; a pseudonym \"Φ-XXXXXXXXXX\" for a natural-person contractor; null when the counterparty is a redacted natural person"

Changed2 schema fields changedAug 27, 2026

addedInput schema / properties / deadline_after

Added value: +{
+  "description": "ISO date (YYYY-MM-DD). Only acts whose submission deadline is on/after this date. Pass TODAY to get OPEN tenders — the ones a supplier can still bid on. Combine with status=\"tender\".",
+  "type": "string"
+}

addedInput schema / properties / region

Added value: +{
+  "description": "NUTS region code prefix, e.g. EL30 (Attica), EL52 (Central Macedonia). Matches by prefix, so EL3 covers all of Attica.",
+  "type": "string"
+}

First observedAug 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: a paginated envelope where 'next' is a page number or null, redaction of natural-person counterparties, and the warning that amount_net cannot be summed for spend. These are non-obvious traits an agent needs before calling.

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?

Front-loaded with the verb, resource and sources, and the most valuable operational rules (open-tender recipe, no-summing warning) are stated crisply. However, the long enumerated filter list partially echoes the input schema, so a few phrases do not fully earn their place.

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?

For an 18-parameter search with an output schema present, the description covers everything an agent needs: source/status vocabularies, signal meanings, pagination semantics, and the aggregation pitfall with the correct alternative tools. Return-value detail is appropriately delegated to the output schema.

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 coverage is already 94%, so the schema carries most parameter meaning, but the description adds cross-parameter semantics: the deadline_after+status combination, and the domain meaning of signals (direct_award = απευθείας ανάθεση, single_bidder = ≤1 bid, cancelled as a published fact). It does not add much beyond the schema for the more mechanical params like page_size or year, keeping this short of a 5.

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?

Starts with a specific verb+resource ('Search Greek public-procurement acts') and immediately scopes it to THREE named cross-linked sources (Διαύγεια, ΚΗΜΔΗΣ, EU TED). This clearly distinguishes it from siblings like get_act, get_chain, rank_entities and spend_by_cpv, which operate on single acts, chains, or aggregates rather than a multi-source 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?

Gives an explicit positive recipe ('deadline_after=TODAY + status=tender ⇒ the OPEN tenders a supplier can still bid on') and an explicit negative rule ('Do NOT sum amount_net across results to get spend — use rank_entities or spend_by_cpv'). Both when-to-use and when-not-to-use with named alternatives are stated.

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

All Diavgis — Greek Public Procurement tools Inspect

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.