Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Get Tender Details

get_tender_details
Read-onlyIdempotent

Retrieve detailed information about a specific Swiss public tender from simap.ch using its project ID, with optional publication and language settings.

Instructions

Get detailed information about a specific tender

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_tender_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoPreferred languageen
fullRawNoInclude the complete unmodified API response as JSON at the end of the output. Verbose — only enable when the structured fields are insufficient.
projectIdYesProject ID (UUID)
publicationIdNoPublication ID (UUID). Defaults to the project's latest publication when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.0
    • changedInput schema / properties / publicationId / description
      Previous value: -"Publication ID (UUID)"New value: +"Publication ID (UUID). Defaults to the project's latest publication when omitted."
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "publicationId"
      -]New value: +[
      +  "projectId"
      +]
  2. Changed1 schema field changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered externally. The description adds nothing beyond that — it does not disclose what 'detailed information' comprises, whether the response is large, or that missing publications are resolved to the latest one.

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?

One short sentence, front-loaded and free of filler, which suits a simple read tool. It is efficient but borders on under-specified rather than deliberately minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-record read with rich annotations and a fully documented schema, an agent has enough to call it with projectId. However, nothing explains the relationship to search_tenders or the shape of the 'detailed information' returned, so the definition is adequate rather than complete.

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% and each parameter carries its own documentation, including the publicationId default-to-latest-publication behavior and the fullRaw verbosity warning. The description contributes no additional parameter meaning, 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 — 'Get detailed information about a specific tender' — which clearly reads as a single-record lookup keyed by identifier, implicitly distinguished from the search_tenders family. It stops short of naming a sibling explicitly, so it lands just below the top band.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: no statement that this should be called after search_tenders returns a projectId, and no mention of when to prefer the publication history or search tools instead. The reader must infer the workflow order from the word 'specific'.

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