Skip to main content
Glama

Public tender / award notice details

get_tender_details
Read-only

Fetch full simap.ch tender notice details—authority, CPV codes, deadlines, lots, and award decisions—using project_id and publication_id from search results.

Instructions

Full simap.ch notice: contracting authority and contact, description, place of performance, CPV codes, procedure, offer deadline, lots and, for award notices, the award decision (winning vendors, awarded price, number of offers, justification). Use project_id + publication_id from search_public_tenders.

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": {
      "project_id": "<project_id>",
      "publication_id": "<publication_id>"
    },
    "name": "get_tender_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for titles and texts (falls back to the notice's original language)de
project_idYesproject_id from search_public_tenders
publication_idYespublication_id from search_public_tenders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully discloses that returned content varies by notice type (tender vs award notice), but adds nothing about rate limits, errors on unknown IDs, or size of payload. Given annotation coverage, a 3 is appropriate.

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?

A front-loaded colon-delimited enumeration of the notice contents followed by one short usage sentence — dense but every item carries information. The field list is long but justified since there is no output schema to describe the response.

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?

With no output schema, the description carries the burden of describing return values and does so by listing the substantive fields, including the award-specific ones. For a three-parameter read-only detail fetch, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both required UUIDs are described there, so the baseline is 3. The description adds a small amount by tying the IDs to their source tool, reinforcing the workflow, but contributes no format or meaning beyond the schema, so it sits just above baseline.

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?

Names a specific resource (simap.ch notice detail) and enumerates its scope: contracting authority, CPV codes, procedure, deadline, lots, and award-decision fields. The clause 'for award notices, the award decision' signals the two notice variants, which clearly separates it from the list-oriented sibling search_public_tenders.

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?

'Use project_id + publication_id from search_public_tenders' establishes the prerequisite step and where the identifiers come from, giving clear usage context. It stops short of stating explicit exclusions (e.g. use search_public_tenders when you only need a list), so it is short of a 5.

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

Deploy Server

Other Tools