Skip to main content
Glama

Search Swiss public tenders & awards

search_public_tenders
Read-only

Search Swiss public procurement tenders on simap.ch and filter by text, canton, project type, notice type, or publication date to find open calls, awards, and related notices.

Instructions

Search procurement projects on simap.ch (Confederation, cantons, municipalities, public companies). Filter by text, cantons of performance, project type, latest notice type (e.g. 'tender' = open calls, 'award_tender' = awarded contracts) and publication date. Needs query (3+ chars) or at least one filter. Results are newest first; pass next_cursor back as cursor for the next page. Example: {query: 'Schulhaus', cantons: ['ZH'], notice_types: ['tender']}.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for titles and texts (falls back to the notice's original language)de
queryNoSearch text (title, description), e.g. 'Reinigung', 'Software', 'Brücke'
cursorNoPagination cursor (`next_cursor` from the previous page)
cantonsNoCantons where the contract is performed, e.g. ['ZH','AG']
cpv_codesNo8-digit CPV codes (see search_cpv_codes), e.g. ['45233140']
notice_typesNoType of the newest notice: tender (open call), award_tender (award), direct_award, advance_notice, revocation, …
project_typesNoconstruction | service | supply | *_competition | *_study | request_for_information
published_fromNoNewest notice on/after this date (YYYY-MM-DD)
published_untilNoNewest notice on/before this date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds behavior beyond that: results are ordered newest-first, and `next_cursor` must be fed back as `cursor` for the next page — practical pagination knowledge not in the schema. It stops short of stating page size or result fields, which keeps it below a 5.

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 purpose, then filters, then the hard precondition, then pagination, then an example — no filler sentences. The trailing example is compact and demonstrates filter combination, though it partially restates the filter list.

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?

For a 9-parameter search tool with no output schema, the description covers scope, filter semantics, the query-or-filter requirement, ordering, and pagination continuation. What remains thin is the return payload shape beyond the cursor, which an agent must discover empirically.

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 100%, so the baseline is 3. The description nonetheless clarifies a genuinely non-obvious semantic: filtering is on the *latest* notice type, with 'tender' meaning open calls and 'award_tender' meaning awarded contracts — a distinction the enum alone does not explain.

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?

States a specific verb+resource ("Search procurement projects on simap.ch") and scopes the covered publishers (Confederation, cantons, municipalities, public companies). This is clearly distinguishable from siblings like search_companies or search_cpv_codes, which cover different corpora.

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

Usage Guidelines4/5

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

Gives a concrete invocation precondition ("Needs `query` (3+ chars) or at least one filter") and enumerates the filter axes, plus a worked example combining them. It does not name an alternative tool or state when not to use it, but the contextual guidance is clear enough to act on.

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

Deploy Server

Other Tools