Skip to main content
Glama

Simap

by io.github.pipeworx-io

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.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "cantons": "ZH,GE",
+    "days_back": 7
+  },
+  {
+    "days_back": 30,
+    "lang": "fr",
+    "pub_types": "award"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, etc. The description adds behavioral context: results are newest first, 20 per page with cursor pagination, and it covers federal, cantonal, and municipal notices. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, with two sentences that immediately state the purpose and key features. No unnecessary words; every sentence adds value.

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?

Given the complexity of 5 optional parameters and no output schema, the description adequately covers what results to expect (newest first, 20 per page, cursor pagination) and the data source (simap.ch). It also mentions it is a wrapper over simap_search for context.

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% with descriptions for all 5 parameters. The description adds the default for days_back (7) and mentions that cantons and pub_types are optional filters with comma-separated values, but this adds only marginal value over the schema. 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?

The description clearly states it lists the most recent Swiss public procurement notices from simap.ch, using a specific verb ('List') and resource ('Swiss public procurement notices'). It distinguishes itself from the sibling tool simap_search by calling itself a 'convenience wrapper' and specifying its focus on recent notices with a days_back parameter.

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?

The description explains when to use this tool: for monitoring recent tenders with days_back, optionally filtered by canton or publication type. It also positions itself as a convenience wrapper over simap_search, implying that for more advanced search, one should use simap_search. However, it does not explicitly state when not to use it or list alternatives beyond simap_search.

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

All Simap toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

There are several tools with overlapping query responsibilities: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-variants of the same router, and bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunity discovery. An agent must read the long descriptions carefully to distinguish them, and some variants are behaviorally identical today.

Naming Consistency3/5

All names are readable snake_case, but the verb_noun convention is not consistently applied: some are clean verb phrases like validate_claim and discover_tools, while others are noun phrases like entity_profile, recent_alerts, or simap_project. The prefixed groups (polymarket_*, pipeworx_*) help, but the overall naming style is mixed.

Tool Count2/5

34 tools is above the heavy range, and the set is inflated by redundant router variants, five overlapping Polymarket tools, and loosely related utilities like generate_llms_txt and scan_dependency. The server is named Simap but only three tools relate to Swiss procurement, making the scope feel bloated and misaligned.

Completeness4/5

For an information-retrieval-style server, the core workflows are well covered: discovery, routing, grounded answers, entity resolution, profiles, comparisons, fact-checking, subscriptions, and memory. The main gaps are minor, such as updating a subscription in place or deeper native Simap-specific actions, and those can be worked around.

Resources