Skip to main content
Glama

getecoback-climate-weather

textil_naht_flaeche_restwasserprofil

Read-only

Restwasser in zwei vorhandenen Stoffproben je 100 g Trockenmasse vergleichen — Compare seam and panel dry-back measurements on a common mass basis.

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": {
      "bedingungen_gleich": "<bedingungen_gleich>",
      "naht_trocken_g": "<naht_trocken_g>",
      "naht_aktuell_g": "<naht_aktuell_g>",
      "flaeche_trocken_g": "<flaeche_trocken_g>",
      "flaeche_aktuell_g": "<flaeche_aktuell_g>",
      "vergleichsspanne": "<vergleichsspanne>"
    },
    "name": "textil_naht_flaeche_restwasserprofil"
  }
}

Input Schema

NameRequiredDescriptionDefault
naht_aktuell_gYesGemessene aktuelle Masse der Nahtprobe.
naht_trocken_gYesBekannte Trockenmasse der Nahtprobe.
vergleichsspanneYesEigene kombinierte Unsicherheit in g Restwasser je 100 g Trockenmasse.
flaeche_aktuell_gYesGemessene aktuelle Masse der Flächenprobe.
flaeche_trocken_gYesBekannte Trockenmasse der Flächenprobe.
bedingungen_gleichYesStammen beide Proben aus demselben Aufbau und Messzeitpunkt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 closed-world, non-mutating calculation. The description adds that the comparison is normalized to a common mass basis and involves two already-existing samples, but it does not say how vergleichsspanne is applied (tolerance gate?), what happens when bedingungen_gleich is false, or what the result looks like.

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 statement with the core operation first and a bilingual gloss second; no padding or repetition. The English half is largely a translation rather than added information, which keeps it just short of a 5.

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?

Against a six-parameter, fully required computation with no output schema and only partial annotations, the description covers the purpose but omits the decision logic an agent needs — notably whether the result is a pass/fail against the user-supplied uncertainty span and whether a false conditions flag invalidates the comparison. Minimal but not sufficient for the tool's complexity.

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 all six parameters are already documented in the input schema. The description only reinforces the unit context ('je 100 g Trockenmasse') that underpins vergleichsspanne, adding marginal meaning beyond the schema — the baseline 3 applies when the schema does the heavy lifting.

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 verb (compare) and resource (residual water in two existing fabric samples, seam vs. panel), plus the normalization basis (per 100 g dry mass). That is enough to distinguish it from measurement-oriented siblings, though it never names an alternative tool by name, so the differentiation is implicit rather than explicit.

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?

The word 'vorhandenen' implies the samples already exist and this is a computation over known dry and current masses, which is a useful hint. Beyond that there is no when-to-use guidance, no prerequisite (e.g., both samples must share the same build/time point — which the schema's bedingungen_gleich actually encodes), and no stated alternative for a single-sample 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