Skip to main content
Glama

getecoback-climate-weather

entfeuchter_kalt_modellbeleg

Read-only

Kaltkeller-Daten für die genaue Entfeuchtervariante nachschlagen — Retrieve verified cold-room evidence and limitations for an exact model.

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": {
      "model": "<model>"
    },
    "name": "entfeuchter_kalt_modellbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModellschlüssel: meaco-one-20 = Arete One 20L, meaco-two-12 = Arete Two 12L, stadler-lukas = Lukas weiss L-031E.

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 safety and scope are covered structurally. The description adds that results are 'verified' and include 'limitations', which usefully tells the agent to expect caveats rather than raw numbers, but it says nothing about what the record contains, how it is formatted, or what happens for a model with sparse evidence.

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?

A single compact sentence pair with the lookup target front-loaded and no filler. The German and English render identical content, which is mildly redundant but consistent with an evidently bilingual toolset, and nothing is buried at the end.

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 one-parameter, read-only, closed-world lookup, the description covers purpose and the existence of limitations, and no output schema exists to defer to. However, 'evidence and limitations' is vague about what the record actually returns, leaving the agent without expectations about the response shape.

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 the single enum parameter already documents each model key with a human-readable mapping, so the schema carries the parameter burden. The phrase 'exact model' reinforces that the parameter selects one variant rather than a filter set, but adds no syntax or selection guidance beyond the schema.

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 action ('nachschlagen' / 'Retrieve') and a specific resource ('cold-room evidence and limitations for an exact model'), so the agent knows this is a per-model evidence lookup rather than a comparison or measurement tool. It stops short of distinguishing itself from nearby siblings like entfeuchter_kalt_messvergleich, which the agent must infer from the model-scoped framing.

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: retrieving data 'for an exact model' suggests this is the tool to call once a specific unit is identified, as opposed to a cross-model comparison. There is no explicit statement of when not to use it, no prerequisites, and no named alternative for the comparison case.

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