Skip to main content
Glama

getecoback-climate-weather

raumdaten_altfeld_verwendung_pruefen

Read-only

Beim Import von EcoBack-Raumdaten veraltete Feuchte- oder Kapazitätsdeutung erkennen — Check old table fields before using sizing data in a new tool.

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": {
      "version": "<version>",
      "feld": "<feld>",
      "zweck": "<zweck>"
    },
    "name": "raumdaten_altfeld_verwendung_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
feldYesVerwendetes Datenmerkmal.
zweckYesGeplante Weiterverwendung.
versionYesFormatversion im übernommenen Export.

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 locality are covered. The description adds domain context (EcoBack import, legacy fields), but says nothing about what the check yields, whether it blocks an import, or how severity is expressed — notable given there is 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?

Two compact clauses, front-loaded with the situation (EcoBack import) before the action. The German/English duplication is mildly redundant but short enough that it does not cost much.

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 read-only three-enum check tool with full schema coverage, the essentials for calling it are present. However, with no output schema, the description should at least indicate the nature of the result (verdict vs. warning) and what the agent should do with it; that gap leaves the loop open.

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% with all three parameters enumerated and briefly described, so the schema carries parameter meaning. The description adds no interpretation of the three axes (field, purpose, format version) — e.g. what 'unbekannt' implies — so the baseline of 3 applies.

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?

Names a specific resource and action: detecting outdated humidity or capacity interpretation in imported EcoBack room data, and checking old table fields before reusing sizing data. An agent can distinguish it from pruning-style siblings like heizkoerper_kalt_pruefen by its legacy-import domain, though the verb is embedded in a German/English fragment pair rather than stated as one crisp operation.

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?

Gives an implicit trigger — call it during import, before using sizing data in a new tool — which is real usage context. It names no alternatives or exclusion cases and does not say what to do when the check flags an outdated field, so guidance stops short of explicit when/when-not 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