Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Search Procurement Offices

search_proc_offices
Read-onlyIdempotent

Find Swiss public procurement offices by name or parent institution to identify the responsible authority for a tender.

Instructions

Search public procurement offices by name or institution

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": "search_proc_offices"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoName to search (min 3 characters)
institutionIdNoFilter by parent institution (UUID)

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.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint, so the safety profile is covered. The description contributes nothing beyond that — no result limits, pagination, ordering, or what an empty search returns — and largely restates the title.

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 ten-word sentence with no filler, leading with the verb and resource. Nothing to trim.

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 simple two-optional-parameter search tool with full annotation coverage and no output schema, this is minimally adequate. It stops short of telling the agent how name and institution filters interact or how many offices come back, which are the remaining practical unknowns.

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%, so both parameters are already documented with type, min length, and UUID format. The description's 'by name or institution' merely maps loosely to those two fields without adding semantics such as whether they combine as AND or are individually optional.

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 ('Search') and a specific resource ('public procurement offices'), plus the two axes it can be searched on. It distinguishes itself from search_tenders and the browse_* tree tools by naming the office entity, though it does not explicitly contrast with them.

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

Usage Guidelines3/5

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

Usage is only implied: the 'by name or institution' phrasing hints that either parameter can drive the lookup, but there is no statement of when to prefer this tool over list_institutions or browse_oag_tree, nor any exclusion conditions.

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