simap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_tendersB | Search public tenders on simap.ch with filters by date, canton, CPV codes, and other criteria |
| get_tender_detailsC | Get detailed information about a specific tender |
| search_cpv_codesB | Search CPV (Common Procurement Vocabulary) codes by keyword or partial code number |
| list_cantonsA | List all Swiss cantons with their codes (useful for search filters) |
| search_bkp_codesB | Search BKP (Swiss construction cost plan) codes by keyword or number |
| search_npk_codesA | Search NPK (standardized positions catalog) codes by keyword or number |
| search_oag_codesA | Search OAG (object type classification) codes by keyword or number |
| browse_cpv_treeC | Browse the CPV code hierarchy (shows subcategories of a parent code) |
| browse_bkp_treeA | Browse the BKP code hierarchy (Swiss construction cost plan) |
| browse_npk_treeC | Browse the NPK code hierarchy (standardized positions catalog) |
| browse_oag_treeC | Browse the OAG code hierarchy (object type classification) |
| list_institutionsA | List Swiss public institutions (Confederation, cantons, municipalities) that publish tenders |
| get_publication_historyC | Get the publication history for a project (corrections, awards, etc.) |
| search_proc_officesB | Search public procurement offices by name or institution |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have clear, distinct roles: tender search/detail, code browsing/searching, and canton listing are easy to tell apart. However, list_institutions and search_proc_offices overlap somewhat, and search_oag_codes vs browse_oag_tree could confuse an agent without reading the descriptions carefully.
All tools follow a consistent snake_case verb_noun pattern using get, list, search, or browse. The verbs map predictably to operations, and abbreviations like cpv, bkp, npk, and oag are used consistently across search and browse tools.
With 14 tools, the server stays within the ideal range and each tool earns its place in the Swiss public procurement workflow. The eight code-related tools are justified by four distinct code systems, each needing both search and hierarchy browsing.
The core workflows of searching tenders and retrieving tender details are well covered, along with code hierarchies and institution lookup. Minor gaps exist: there is no direct institution-detail endpoint or tenders-by-institution endpoint, and no document/attachment access, but agents can work around these via search_tenders filters and get_tender_details.