Skip to main content
Glama

getecoback-climate-weather

verdunster_raumfeuchte_versuchsabbruch_zielbelegt

Read-only

Berichtet einen örtlichen Erfolg und eine spätere vorgegebene Abbruchmarke als getrennte Befunde — Preserve a measured local improvement and a later user-set trial stop as separate outcomes.

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": {
      "lokaler_nutzen": "<lokaler_nutzen>",
      "gestoppt": "<gestoppt>",
      "nutzzeit": "<nutzzeit>"
    },
    "name": "verdunster_raumfeuchte_versuchsabbruch_zielbelegt"
  }
}

Input Schema

NameRequiredDescriptionDefault
gestopptYesBelegter Grund des Testendes.
nutzzeitYesBis Testende dokumentierte aktive Nutzungsdauer in Minuten.
lokaler_nutzenYesAusgang der örtlichen Probe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows nothing is mutated and no external lookup occurs. The description is consistent with that ('berichtet' rather than 'speichert'), and it adds the behavioral rule that the two findings must be preserved separately. It adds nothing further about validation behavior, error cases, or what the caller receives back, which keeps it at an adequate rather than rich level.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and the key constraint is front-loaded, which is good. However, it is effectively stated twice – a German sentence immediately restated in English – so roughly half the text is redundant for any agent that reads either language. The bilingual hedge adds accessibility but costs conciseness.

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?

Three required parameters, no output schema, and a minimal annotation set mean the description should carry more weight than it does. It explains the relationship the tool encodes but never says what comes back (a consolidated record? a verdict?) nor how conflicting inputs are treated, leaving the agent to guess at the result. Adequate for a small validation/recording tool, but with visible gaps.

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 description coverage is 100% and the two enum parameters already carry their own descriptions and value lists, so the schema does most of the work. The description does add real meaning by marking the temporal ordering between lokaler_nutzen (earlier measured improvement) and gestoppt (later user-set stop) and by framing them as independent findings. That is a genuine contribution but it is thin and does not touch nutzzeit at all.

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 the two things the tool reports – a measured local improvement and a later user-set trial stop – and the verb 'berichtet/preserve' makes the recording/consolidation intent clear. The core semantic point (keep the two findings separate rather than collapsing them into one verdict) is stated explicitly, which lets an agent tell it apart from aggregation-style siblings. It falls short of a 5 because the operational nature (does it validate, store, or just format a verdict?) stays implicit.

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 only implied: an agent infers it should call this when it has both a local improvement result and a trial-stop reason that must not be conflated. There is no explicit when-to-use or when-not-to-use statement and no alternative named for the case where only one of the two findings exists. The 'separate outcomes' instruction does guide invocation somewhat, but no prerequisites or exclusions are given.

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