Skip to main content
Glama

Simap Recent

simap_recent
Read-onlyIdempotent

List the most recent Swiss public procurement notices from simap.ch (government tenders and award decisions across Switzerland, federal, cantonal, municipal). Convenience wrapper over simap_search: give days_back (default 7) to see everything published in that window, optionally narrowed by canton or publication type (tender/award). Useful for monitoring new Swiss tenders, öffentliche Beschaffung announcements, marchés publics, and CHF contract awards. Newest first, 20 per page with cursor pagination.

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": {
      "cantons": "ZH,GE",
      "days_back": 7
    },
    "name": "simap_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage: "de" (default), "fr", "it", or "en".
cantonsNoSwiss canton code(s), comma-separated, e.g. "ZH", "VD,GE".
days_backNoHow many days back to look (1-90). Default 7.
last_itemNoPagination cursor (`next_cursor` from the previous response).
pub_typesNoPublication type(s), comma-separated: "tender", "award".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / days_back / description
      Previous value: -"How many days back to look (1–90). Default 7."New value: +"How many days back to look (1-90). Default 7."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cantons": "ZH,GE",
      +    "days_back": 7
      +  },
      +  {
      +    "days_back": 30,
      +    "lang": "fr",
      +    "pub_types": "award"
      +  }
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds value beyond them by disclosing result ordering ('Newest first'), page size (20 per page) and cursor pagination, which the annotations say nothing about. It does not mention rate limits or what fields each notice carries, but the ordering/paging disclosure is the operationally important part.

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-loads what the tool returns, then the simap_search relationship, then narrowing options, then ordering and paging — a sensible information order. It is somewhat dense in the third sentence, where multilingual keyword variants ('öffentliche Beschaffung', 'marchés publics', 'CHF contract awards') pad the text, though those arguably aid retrieval matching.

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 five-parameter, zero-required read tool with full schema coverage and no output schema, the description covers scope, the alternative tool, filtering options, sort order and pagination — everything needed to call it correctly. The only real gap is that it does not say how results relate to simap_search's broader filtering (e.g. that this tool cannot filter by keyword or buyer).

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 description coverage is 100%, so all five parameters are already documented in the schema, including the days_back default and canton code format. The description restates days_back's default and the canton/pub-type narrowing but adds no format or constraint detail beyond the schema, and never mentions lang or last_item directly (pagination is only implied). Baseline 3 is appropriate.

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 ('List') and resource ('most recent Swiss public procurement notices from simap.ch'), scoping it to government tenders and award decisions at federal, cantonal and municipal levels. It also explicitly positions itself as a 'convenience wrapper over simap_search', so an agent can distinguish it from the sibling without opening either schema.

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 concrete usage context: supply days_back (default 7) to see everything published in a window, optionally narrowing by canton or publication type, and names monitoring of new Swiss tenders as the intended scenario. It names simap_search as the underlying alternative but stops short of an explicit 'use simap_search instead when...' rule, leaving the boundary to inference.

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.