Skip to main content
Glama

getecoback-raumklima

punktwaerme_aufgabenmix_ungepruefte_kaltphase

Read-only

Vor der Übertragung einer Werkstattmessung ermitteln, welche tatsächlich vorkommenden Startbedingungen noch keinen passenden Versuch haben — Audit coverage of real cold-start task classes.

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": {
      "mild_aufgaben": "<mild_aufgaben>",
      "kalt_aufgaben": "<kalt_aufgaben>",
      "mild_mit_messung": "<mild_mit_messung>",
      "kalt_mit_messung": "<kalt_mit_messung>"
    },
    "name": "punktwaerme_aufgabenmix_ungepruefte_kaltphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
kalt_aufgabenYesZahl solcher Blöcke in der eigenen kalten Startklasse.
mild_aufgabenYesZahl vergangener beaufsichtigter Arbeitsblöcke in der selbst definierten milden Startklasse.
kalt_mit_messungYesDavon kalte Blöcke mit vollständigem vergleichbarem Wärmeprotokoll.
mild_mit_messungYesDavon milde Blöcke mit vollständigem vergleichbarem Wärmeprotokoll.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 this is a safe, closed computation. The description adds the decision context (it is a gate applied before transferring a workshop measurement), but says nothing about how the four counts are combined, whether mild and cold classes are reported separately, or what the caller should expect to receive.

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 short clauses with the trigger front-loaded and the purpose immediately after. The English gloss partially restates the German sentence, a mild redundancy, but nothing else is padded.

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

Completeness2/5

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

With four required numeric inputs and no output schema, the description is the only place that could explain what the audit yields — the number of unrepresented cold-start classes, a coverage ratio, or a list. It never does, so an agent knows when to call this but not what it will get back, which is a significant gap for a pure-computation tool.

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 every one of the four required properties carries a precise German definition, so the schema fully carries parameter meaning. The description never references the mild/cold or with-measurement/without-measurement split, adding no semantics beyond the schema — baseline 3 is appropriate.

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 German clause names a concrete operation — determining which actually occurring start conditions still lack a matching trial before a workshop measurement is transferred — and the English gloss frames it as an audit of cold-start task-class coverage. It stops short of saying what the call actually returns (a count of uncovered classes? a ratio?) and never contrasts itself with the many sibling punktwaerme coverage tools.

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?

'Vor der Übertragung einer Werkstattmessung' gives a genuine usage trigger (a pre-transfer gate check), which is more than most siblings offer. There is no when-not guidance and no named alternative for the adjacent questions covered by siblings such as punktwaerme_aufgabenzeit_ausfallursachen or punktwaerme_messraster_zonen_verteilung_spannweite, 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