zzd: Swiss everyday data

Map poster of a place (MappaMuse)

find_map_posters

Read-onlyIdempotent

Find the ready poster page for a town or place on MappaMuse (mappamuse.zzd.ch, personalised map posters printed to order, by zzd), with the sizes and prices that page lists, in CHF. Any other place can be designed on the custom-poster page. The result links the page; the page and checkout are binding.

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": {
      "place": "<place>"
    },
    "name": "find_map_posters"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of names and links. Default de.
`place`	Yes	A town or place, e.g. 'Aarau', 'Lugano'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: prices are listed in CHF, the result links to the page, and the page and checkout are binding (i.e., returned prices are indicative rather than authoritative). It stops short of stating what happens when no ready page exists beyond pointing at the custom page.

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?

Three sentences, front-loaded with the primary action and the returned data, followed by the fallback route and the binding-price caveat. The parenthetical vendor gloss ('personalised map posters printed to order, by zzd') and the raw domain are slightly noisy but do establish provenance. No sentence is redundant.

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

Completeness4/5

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

With only two parameters, no output schema, and annotations covering safety, the description supplies what an agent needs: what is returned (page link, sizes, prices in CHF) and the caveat that the page/checkout governs. Missing is any explicit statement of the not-found case, which is only implied by the custom-poster fallback.

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%, so both parameters are already documented in the schema, and the description adds little beyond confirming that 'place' means a town or place. The 'lang' parameter, including its default and enum, is not mentioned at all in the description. Baseline 3 applies when the schema carries the parameter burden.

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 states a specific verb and resource: find the ready-made poster page for a town or place on MappaMuse, returning that page's sizes and prices in CHF. It also distinguishes the case it does not cover (places without a ready page go to the custom-poster page). Sibling tools are in unrelated domains, so no sibling differentiation was needed, which keeps this just short of a 5.

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?

It gives a clear when-to-use (a town or place that already has a ready poster page) and a when-not with the alternative route (any other place is designed on the custom-poster page). The alternative is a web page rather than a sibling tool, so the routing guidance is useful but not framed against other MCP tools.

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

All zzd: Swiss everyday data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?