Skip to main content
Glama

getecoback-climate-weather

gebraucht_auflagepads_unterschied_kompressionsprobe

Read-only

Zwei gleichartige gebrauchte Auflagen anhand einer bereits dokumentierten Vergleichsmessung unterscheiden — Compare a pad pair’s observed compression without making a material-lifetime 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": {
      "bedingungen_gleich": "<bedingungen_gleich>",
      "a_unbelastet": "<a_unbelastet>",
      "a_belastet": "<a_belastet>",
      "b_unbelastet": "<b_unbelastet>",
      "b_belastet": "<b_belastet>",
      "messspanne": "<messspanne>"
    },
    "name": "gebraucht_auflagepads_unterschied_kompressionsprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_belastetYesDicke A bei gleicher dokumentierter Belastung.
b_belastetYesDicke B unter der gleichen Belastung.
messspanneYesSelbst bestimmte kombinierte Unsicherheit der Differenzen.
a_unbelastetYesDicke A unbelastet in mm.
b_unbelastetYesDicke B unbelastet in mm.
bedingungen_gleichYesSind trockener Zustand, Auflagentyp, Belastung und Messstelle beider Proben vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation. The description adds useful context about input provenance and the limitation against lifetime claims. However, it does not explain how the comparison is performed, what result is produced, or how the uncertainty parameter affects the distinction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact statement with the core action and the key limitation front-loaded. The bilingual phrasing adds a brief clarification without unnecessary repetition.

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?

The input schema and annotations cover the required inputs and safety profile well. Because there is no output schema, the description should ideally explain what the distinguishing result looks like and how the uncertainty measure is used, but it does not. It is adequate but incomplete for a comparison tool with six required inputs.

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?

All six parameters have schema descriptions at 100% coverage, so the schema carries the parameter semantics. The description only alludes generally to observed compression and documented comparative measurement, adding no new meaning about individual parameters or the required equality condition.

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 uses a specific verb, 'unterscheiden' (distinguish), and a specific resource, two similar used pads, scoped to an already documented comparative measurement. The English clause clarifies that this is an observed-compression comparison rather than a material-lifetime judgment. It does not explicitly distinguish itself from sibling tools, so it stops short of a 5.

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?

It gives a clear use condition: there must already be a documented comparison measurement. It also gives a meaningful boundary: no material-lifetime claim should be derived. It does not name alternative tools or explain when another pad-related tool would be more appropriate.

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