Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Compare Cities Table

compare_cities_table

Compare Aare river swimming conditions across cities with a sortable, searchable table. See water temperature, flow, and BAFU safety ratings for each location.

Instructions

Show a sortable, searchable table comparing Aare conditions across cities.

Header summary cards use the aare.guru cyan (#2be6ff) accent. Safety column uses BAFU color coding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNode
citiesNoCity identifiers to compare. If omitted, compares all available cities.

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful UI behavior details: sortable, searchable, header card accent color, and BAFU safety color coding. However, it does not explicitly state read-only behavior, data freshness, or any side effects.

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?

The description is two concise sentences, front-loaded with the main purpose and followed by relevant visual specifications. Every sentence adds useful detail without padding.

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?

For a simple table-view tool with no required parameters and no output schema, the description is mostly complete. It explains the display type and notable visual behavior, though it could optionally mention what happens when 'cities' is omitted or how language selection affects output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, with the 'cities' parameter described but 'lang' undocumented. The description does not compensate for the gap: it mentions cities only conceptually and never addresses the language parameter or how city identifiers are supplied.

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 clear verb and resource: 'Show a sortable, searchable table comparing Aare conditions across cities.' It is easy to understand what the tool renders, though it does not explicitly differentiate itself from the sibling 'compare_cities' tool beyond implying a table presentation.

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 guidance on when to choose this tool over alternatives like 'compare_cities' or other view tools. The description implies comparison use, but it does not state context, exclusions, or alternatives.

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