Skip to main content
Glama

getecoback-climate-weather

messreihe_grenzwert_rundung_faelle

Read-only

Beim Zählen von Feuchtewerten nahe der Prüfschwelle sichere und rundungsbedingt offene Fälle trennen — Bound the count above a threshold from three categories of rounded observations.

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": {
      "sicher_unterhalb": "<sicher_unterhalb>",
      "sicher_ab_schwelle": "<sicher_ab_schwelle>",
      "spannweite_schneidet": "<spannweite_schneidet>",
      "ungueltige_beobachtungen": "<ungueltige_beobachtungen>"
    },
    "name": "messreihe_grenzwert_rundung_faelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
sicher_unterhalbYesZahl der Beobachtungen, deren ganze Rundungsspanne unter der Schwelle liegt.
sicher_ab_schwelleYesZahl der Beobachtungen, deren ganze Rundungsspanne auf oder über der Schwelle liegt.
spannweite_schneidetYesZahl der Beobachtungen mit Rundungsspanne auf beiden Seiten der Schwelle.
ungueltige_beobachtungenYesWeitere nicht auswertbare oder fehlende Beobachtungen dieser Reihe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful domain semantics about rounding-induced ambiguity and the three-category split, but it never states what the tool returns (e.g., a lower/upper bound, a classification count) and gives no result-format context despite there being no output schema.

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 short and front-loads the domain context. It does repeat the same content in German and English, which is somewhat redundant, but the total length is small and no sentence is padding.

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

Completeness3/5

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

For a four-parameter computation tool with no output schema, the definition explains the input categorization but leaves the output entirely unspecified. An agent knows what to supply but not what it will receive, which is a meaningful completeness gap for a bounding calculation.

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 100% and each of the four parameters already carries a clear German description, so the schema does the heavy lifting. The description adds only high-level framing — 'three categories of rounded observations' — which loosely maps to the three threshold categories but does not explain how the fourth parameter (invalid observations) affects the bound.

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 names a specific operation — separating safe counts from rounding-open cases when counting humidity values near a test threshold — and frames it as bounding a count above a threshold from three rounded-observation categories. It is more specific than a tautology, though it does not name a sibling to differentiate from and the verb phrasing ('trennen' / 'Bound the count') is slightly abstract.

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?

Usage is implied by the domain framing: this is for measurement series near a threshold where rounding creates ambiguity. There is no explicit when-to-use/when-not-to-use statement and no alternative sibling tool is referenced, so the agent must infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources