Skip to main content
Glama

getecoback-raumklima

daemmvorhang_stoff_saisonbeleg

Read-only

Bei Thermovorhängen sommerlichen Sonnenschutz und winterliche Dämmversprechen prüfen — Identify the evidence needed for a thermal curtain performance claim.

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": {
      "zweck": "<zweck>",
      "fensteraufbau": "<fensteraufbau>",
      "montage_gleich": "<montage_gleich>",
      "messgroesse": "<messgroesse>"
    },
    "name": "daemmvorhang_stoff_saisonbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
zweckYesGewünschter Einsatz.
messgroesseYesHat der Anbieter zur angestrebten Wirkung eine konkrete Messgröße und Methode genannt?
fensteraufbauYesIst der Fensteraufbau des Prüfbelegs angegeben?
montage_gleichYesEntspricht die Montage der eigenen Situation, einschließlich Abstand und Abdeckung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 is covered. The description adds domain framing (curtain performance claims need evidence of measurement, window construction, and mounting match), which is genuinely useful context. It does not disclose what the invocation returns (a verdict, a checklist, gap flags), which is a meaningful omission for a rubric-style tool.

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, front-loaded with the German framing then an English gloss. The bilingual duplication is mild redundancy but aids comprehension given the obscure name. No filler otherwise.

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?

Inputs are fully documented by the schema and the tool is read-only, so the essential calling information exists. But there is no output schema, and the description never explains what the agent receives back from this evidence check — the biggest remaining gap for a four-required-boolean evaluator.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with an enum and per-field descriptions, so the baseline is 3. The description pushes slightly higher by tying the fields together into a coherent concept — it frames the whole input set as the evidence needed to back a curtain performance claim, which clarifies why messgroesse, fensteraufbau, and montage_gleich belong together. It does not add format or value details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific domain action (checking summer sun-protection and winter insulation claims for thermal curtains) and a specific goal (identifying the evidence a performance claim requires). However, the opaque German tool name carries no signal, and the verb 'prüfen / identify' leaves ambiguous whether the tool evaluates supplied evidence, asks for it, or returns a checklist. An agent gets the topic but not a 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no indication of when to use this versus alternatives, no prerequisites, and no exclusion criteria. The description says nothing about routing among the many sibling check tools; the agent must infer usage purely from the domain phrase.

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