Skip to main content
Glama

getecoback-raumklima

wandfleck_umriss_aenderung_protokollieren

Read-only

Größenänderung einer beobachteten Stelle anhand eines wiederholten Umrissmaßes einordnen — Record changes in a bounding rectangle, not a moisture diagnosis.

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": {
      "erste_breite_cm": "<erste_breite_cm>",
      "erste_hoehe_cm": "<erste_hoehe_cm>",
      "neue_breite_cm": "<neue_breite_cm>",
      "neue_hoehe_cm": "<neue_hoehe_cm>",
      "gleiche_methode": "<gleiche_methode>"
    },
    "name": "wandfleck_umriss_aenderung_protokollieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
neue_hoehe_cmYesHöhe bei der Wiederholung.
erste_hoehe_cmYesHöhe dieses Rechtecks beim ersten Foto.
neue_breite_cmYesBreite bei der Wiederholung am selben Ort.
erste_breite_cmYesBreite des kleinsten eingeschlossenen Rechtecks beim ersten Foto.
gleiche_methodeYesMaßstab, Betrachtungsort, begrenzte Stelle und Messmethode gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety profile is covered by structured data. The description adds scope framing (size change of an observed spot, not a diagnosis) but says nothing about what the 'Einordnung' output looks like or what happens when gleiche_methode is false, even though there is no output schema to fall back on. Adequate, not rich.

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 front-loaded sentence with the core action first and the exclusion second; nothing is padded. The German/English duplication is mildly redundant but serves as a clarifying gloss rather than filler.

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?

With five required numeric/boolean parameters, no output schema, and a tool that classifies rather than just stores, the definition should say what the classification means or how a false gleiche_methode is handled. It covers intent and scope but leaves the result semantics entirely unstated, which is a real gap for the calling agent.

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%, so every parameter (erste/neue Breite/Höhe, gleiche_methode) is already self-documenting. The description's 'wiederholtes Umrissmaß' and 'bounding rectangle' loosely frame the two measurement points but add no units, tolerance, or handling detail beyond the schema. Baseline 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?

The English half states a concrete verb and resource: 'Record changes in a bounding rectangle' for a repeatedly measured observed spot. It also separates itself from the diagnostic siblings with 'not a moisture diagnosis', so an agent can tell it apart from tools like bad_feuchte_erholung_protokoll or befeuchter_weissen_belag_einordnen. The German 'einordnen' is slightly vaguer than 'record', costing a point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The phrase 'anhand eines wiederholten Umrissmaßes' establishes the precondition that a repeat measurement exists, and 'not a moisture diagnosis' is an explicit when-not exclusion. What is missing is a named alternative for the actual diagnosis case, so the agent must infer where to go instead.

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