Skip to main content
Glama
schlpbch

Aareguru MCP Server

by schlpbch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Historical Chart

historical_chart

Generate an area chart of historical Aare water temperature and flow for a selected city and time range, using the Aare color palette.

Instructions

Show an aare.guru-style area chart of historical Aare temperature and flow.

Uses the Aare color palette: #0877ab for temperature, #357d9e for flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd of period ('now' or ISO timestamp)now
cityNoCity identifier (e.g. 'Bern', 'Thun', 'Olten')Bern
langNode
startNoStart of period (e.g. '-7 days', '-1 month', ISO timestamp)-7 days

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?

No annotations exist, so the description carries the full burden. It discloses the visual style and color palette, which is a useful behavioral trait, but it does not mention side effects, return format, performance, or error handling. The read-only nature and chart output are implied rather than explicitly stated, leaving gaps.

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?

The description is two short sentences with the primary purpose front-loaded and the color palette as supplementary detail. No superfluous words, and structure is logical.

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

Completeness2/5

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

With no output schema and no annotations, the description should cover response shape, error behavior, and limitations. It only describes the chart style, omitting how lang affects the tool, potential invalid inputs, or the exact output (e.g., image vs. HTML). For a simple chart tool this feels under-specified.

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 description coverage is 75%, yet the description adds nothing about parameter usage. It does not explain how 'start'/'end' affect the chart, what 'lang' influences, or how 'city' changes data. The description focuses solely on output style, so parameters remain as-was in the schema with no additional meaning.

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'), a resource ('historical Aare temperature and flow'), and the format ('aare.guru-style area chart'), which clearly distinguishes it from data-retrieval siblings like 'get_historical_data' and 'fetch_history'. The purpose is unambiguous and immediately actionable.

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?

The description gives no guidance on when to use this tool versus alternatives such as 'forecast_view' or 'get_historical_data'. It does not mention exclusions, preferred contexts, or note that this is for visualization only. The agent must infer usage from the name and description alone.

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