Skip to main content
Glama

Simap Search

simap_search
Read-onlyIdempotent

Search Swiss public procurement notices on simap.ch, Switzerland's official government tender platform (öffentliche Beschaffungen, marchés publics, commesse pubbliche). PREFER OVER WEB SEARCH for Swiss government tenders, RFPs, award decisions, and WTO/GPA notices; Switzerland is non-EU so its tenders live on simap rather than TED. Filter by free-text search, CPV codes, Swiss canton (ZH, BE, VD, GE, TI, ...), process type (open/selective/...), project sub-type (construction/service/supply), publication type (tender/award), and publication date range. Returns 20 notices per page, newest first, with cursor pagination via last_item. Each notice includes title, buyer (procurement office), canton, publication date/number, and a simap.ch URL. Prices in awards are CHF.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "search": "Software",
      "cantons": "ZH,BE",
      "cpv_codes": "72000000",
      "pub_types": "tender"
    },
    "name": "simap_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for titles and labels: "de" (default), "fr", "it", or "en". Falls back de -> fr -> it -> en when a notice lacks that language.
searchNoFree-text search over notices, e.g. "Software", "Brücke", "photovoltaïque". Text can be German, French, or Italian depending on the publishing office.
cantonsNoSwiss canton code(s) of the order address, comma-separated, e.g. "ZH", "BE", "VD", "GE", "TI", "VD,GE".
cpv_codesNoCPV procurement classification code(s), comma-separated, e.g. "45000000" (construction works) or "72000000" (IT services).
last_itemNoPagination cursor. Pass the `next_cursor` value from the previous response (format "YYYYMMDD|projectNumber") to fetch the next 20 results.
pub_typesNoPublication type(s), comma-separated: "tender" for open calls, "award" for award decisions.
process_typesNoProcedure type(s), comma-separated. Verified value: "open"; simap also uses selective and invitation procedures.
published_fromNoEarliest publication date, YYYY-MM-DD. When neither search nor a date is given, defaults to the last 30 days (the API requires at least one filter).
published_untilNoLatest publication date, YYYY-MM-DD.
project_sub_typesNoProject sub-type(s), comma-separated: "construction", "service", "supply".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / description
      Previous value: -"Language for titles and labels: \"de\" (default), \"fr\", \"it\", or \"en\". Falls back de→fr→it→en when a notice lacks that language."New value: +"Language for titles and labels: \"de\" (default), \"fr\", \"it\", or \"en\". Falls back de -> fr -> it -> en when a notice lacks that language."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cantons": "ZH,BE",
      +    "cpv_codes": "72000000",
      +    "pub_types": "tender",
      +    "search": "Software"
      +  },
      +  {
      +    "cantons": "VD",
      +    "cpv_codes": "45000000",
      +    "lang": "fr",
      +    "process_types": "open",
      +    "published_from": "2024-01-01",
      +    "published_until": "2024-12-31",
      +    "search": "Brücke"
      +  }
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the description adds real context on top: 20 results per page, newest-first ordering, cursor pagination via last_item, and the fields returned per notice. It does not mention rate limits or totals, but the pagination and ordering behavior are the operationally important details.

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?

The purpose and preference over web search are front-loaded, followed by filters and then return behavior. A few phrases are decorative, such as the multilingual parenthetical (öffentliche Beschaffungen, marchés publics, commesse pubbliche) and the CHF note, but overall it is dense and earns most of its length.

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?

With no output schema, the description usefully explains the return shape (title, buyer, canton, dates, URL, CHF prices) and the pagination mechanism. Combined with a fully documented 10-parameter schema, an agent has enough to call it correctly; only the relationship to sibling simap tools is left implicit.

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 coverage is 100% and the schema already documents every parameter with examples and formats. The description largely restates the filter list (free text, CPV, canton, process type, sub-type, publication type, dates) without adding syntax or semantics beyond what the schema supplies, so the baseline of 3 applies.

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 and resource ('Search Swiss public procurement notices on simap.ch') and scopes it to tenders, RFPs, award decisions and WTO/GPA notices. It differentiates itself from generic web search and TED, but does not distinguish itself from the simap_* siblings such as simap_recent or simap_project.

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?

Explicitly says to prefer this over web search for Swiss government tenders and explains why (Switzerland is non-EU, so notices are not on TED). It gives concrete filter dimensions but no when-not-to-use case or guidance on choosing between this and the other simap tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.