Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

City Finder View

city_finder_view

Find the warmest or safest Aare swimming spot by ranking all available cities live by water temperature or safety.

Instructions

Show all cities ranked by water temperature or safety.

Fetches live data for every available city and ranks them so swimmers can instantly find the warmest or safest spot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNode
sort_byNoRanking criterion — 'temperature' (warmest first, default) or 'safety' (lowest flow / safest first)temperature

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.9.0
    • addedInput schema / properties / lang
      Added value: +{
+  "default": "de",
+  "type": "string"
+}
  2. Addedv4.6.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool 'fetches live data for every available city and ranks them,' which is useful behavioral context. However, it does not mention whether the operation is read-only, how many results are returned, or any caching or failure behavior.

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?

Two sentences with no filler. The main action and ranking criteria are front-loaded, and the supporting use-case sentence earns its place by clarifying the intended audience and outcome.

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?

Given no output schema and no annotations, the description covers the core purpose, data scope (all cities), data freshness (live), and ranking criteria. It omits details about output structure and the lang parameter, but for a simple read-only view tool this is nearly complete.

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 50%: sort_by is documented but lang is not. The description reinforces the meaning of sort_by through 'water temperature or safety' and 'warmest or safest spot,' but it adds nothing about the lang parameter, leaving part of the schema under-explained.

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?

The description states a specific verb ('Show') and resource ('all cities ranked by water temperature or safety'), and the use case for swimmers makes the tool's intent unmistakable. This distinguishes it from siblings like get_current_temperature or compare_cities, which focus on single cities or comparisons.

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?

The description implies when to use the tool ('so swimmers can instantly find the warmest or safest spot'), but it does not explicitly contrast it with alternatives or state when not to use it. There is no guidance about choosing this over compare_cities or forecast_view.

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