Skip to main content
Glama
malkreide

swiss-procurement-mcp

by malkreide

search_procurements_detailed

Read-onlyIdempotent

Search Swiss public tenders and fetch full details for the top matches in a single call, replacing separate detail lookups.

Instructions

Answer a question needing both the hit list and each hit's detail in one step, e.g. "which school-building tenders ran in ZH and what BKP codes do they carry?". Prefer this over search_procurements followed by N detail calls.

Search publications and return the FULL record for the top matches at once.

Aggregated entry point for the common "find tenders and show me their details" question: it runs the search and then fetches get_procurement_details for the first top_n hits in parallel, so a typical query is answered in a single tool call instead of a search-then-N-details chain. Each result carries the CPV and Swiss construction codes (BKP, NPK), deadlines and procurement office.

Prefer search_procurements when you only need the summaries or want to paginate; use this when you want the leading hits fully expanded immediately.

Args: top_n: How many of the top hits to expand to full detail (1-5). query, canton, canton_match, cpv_codes, process_type, pub_type, published_from, published_until, language: identical to search_procurements — including the canton_match semantics, which default to matching the procuring body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
countYesNumber of full detail records returned (<= top_n).
sourceYes
resultsYes
match_typeNoexact when results were returned, none when empty.none
provenanceYes
retrieved_atYes
total_matchedNoTotal search hits before the top_n detail cutoff.
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful context: it runs a search then fetches get_procurement_details in parallel for top_n hits, and each result carries CPV/BKP codes, deadlines, and office. This goes beyond basic safety disclosure to explain the composite behavior.

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?

Longer than typical, but well-structured with a <use_case> tag, a one-sentence summary, explanation of aggregation, and an Args block. Every sentence contributes value; no redundancy from the schema.

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 a composite tool with one parameter and a sibling reference, the description covers use case, internal behavior, result contents, alternatives, and parameter semantics. The presence of an output schema lowers the burden for return-value details, making this complete.

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 0% for the single 'args' parameter, but the description explicitly defines top_n as 'How many of the top hits to expand to full detail (1-5)' and states all other params are 'identical to search_procurements', linking to a sibling for full semantics. This compensates for the schema gap well.

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?

Description opens with 'Search publications and return the FULL record for the top matches at once' – a specific verb+resource+scope statement. It also explicitly contrasts with sibling search_procurements, clarifying its unique aggregation behavior.

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?

Provides explicit when/when-not guidance: 'Prefer this over search_procurements followed by N detail calls' and 'Prefer search_procurements when you only need the summaries or want to paginate'. This disambiguates tool selection clearly.

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/malkreide/swiss-procurement-mcp'

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