Read-only student guides to Germany: ten cities, housing, banking, jobs and everyday life.
Scored across 3 tools
get_guide is clearly a content fetch, while list_cities and list_sections both enumerate navigational entry points, so there is some overlap between the two listing tools. The descriptions do distinguish them (cities with entry points vs. sections/languages, optionally scoped by city), so an agent can mostly pick correctly.
All three tools follow the same verb_noun snake_case pattern: get_guide, list_cities, list_sections. The verbs also map cleanly to fetch vs. enumerate semantics.
Three tools is minimal but coherent for a read-only guide server: discover cities, discover sections/languages, fetch content. It is slightly thin—there is no direct search or bulk retrieval—but nothing feels redundant.
The browse-then-fetch lifecycle is covered: list_cities/list_sections provide routes and get_guide retrieves any known public guide, including language and legal-page handling. The main gap is the absence of a search or keyword-lookup tool, which agents must work around via section listings.
Fetch a single published guide as Markdown. Use a route returned by list_sections, / for the homepage, and an optional language code. Only known public guide routes are allowed; legal pages are English-only.
Inputs: route (required), language.
List the ten supported German student cities and their guide entry points.
Inputs: no named parameters.
List city sections, Germany-wide guides and supported language codes. Optionally choose a supported city.
Inputs: city.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.