Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

List Institutions

list_institutions
Read-onlyIdempotent

Retrieve Swiss public institutions (Confederation, cantons, municipalities) that publish tenders, with optional name filtering and language selection.

Instructions

List Swiss public institutions (Confederation, cantons, municipalities) that publish tenders

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_institutions"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for namesen
searchNoFilter by name (min 3 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully supplied elsewhere. The description adds only the domain scope ('that publish tenders') and says nothing about whether results are paginated, complete, or filtered by the tenders qualifier, which is a real ambiguity for an openWorld listing call.

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?

A single sentence with no filler, and the most discriminative information (Swiss public institutions, hierarchy levels, tender-publishing scope) is front-loaded. Nothing could be removed without losing meaning.

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 two-optional-parameter read-only listing tool with a fully documented schema and no output schema, the minimal description is nearly sufficient. What is missing is positioning against the crowded sibling set, particularly list_cantons, which an agent could easily confuse with this tool.

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%, with both 'lang' and 'search' documented in-schema including the enum values and the 3-character minimum. The description mentions neither parameter, so the baseline 3 applies: the schema carries the full burden and nothing extra is added or contradicted.

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?

The description gives a specific verb ('List') and a precisely bounded resource ('Swiss public institutions') with the level hierarchy spelled out in parentheses (Confederation, cantons, municipalities) plus the qualifying trait 'that publish tenders'. It is clearly separable from data-oriented siblings like search_tenders or get_tender_details, though it never distinguishes itself from list_cantons.

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 statement of when to reach for this tool versus list_cantons, search_proc_offices, or browse_oag_tree, all of which touch overlapping organizational data. The only usable cue is implicit: it enumerates institutions rather than tenders. No exclusions or prerequisites are given.

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