Skip to main content
Glama

getecoback-climate-weather

eisprobe_gemessene_schmelzmasse_waermeanteil

Read-only

Rechnet die gemessene Schmelzmasse aus einer vorhandenen reinen Eisprobe in einen theoretischen Wärmeanteil um — Estimate latent heat from measured melting of known pure water ice.

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": {
      "geschmolzen_g": "<geschmolzen_g>",
      "reines_wassereis_belegt": "<reines_wassereis_belegt>"
    },
    "name": "eisprobe_gemessene_schmelzmasse_waermeanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
geschmolzen_gYesGetrennt gewogene, vollständig geschmolzene Eismasse in g.
reines_wassereis_belegtYesBekannte reine Wassereisprobe, getrennt von vorhandenem Wasser oder unbekannter Akkufüllung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world computation with no side effects. The description contributes the fact that the output is a *theoretical* derived quantity rather than a measurement, which is meaningful context, but it says nothing about the model/formula, assumptions (e.g. purity tolerance), or units of the result.

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 operation stated first, keeping it compact and easy to scan. The German and English halves are redundant, which is mild waste but aids disambiguation for mixed-language agents.

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?

For a simple two-parameter calculation tool this covers the input side adequately, but with no output schema the description never indicates what the returned Wärmeanteil looks like (scalar? units? confidence?). That is the one piece an agent cannot recover from structured fields.

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 both parameters (the weighed melt mass in grams and the purity/known-sample boolean) are already fully documented in the schema, and the description adds no further meaning to them. Baseline 3 applies when the schema carries the parameter semantics.

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 transformation (measured melt mass → theoretical latent heat share) rather than restating the tool name, and the German/English pair makes the intent unambiguous. It does not differentiate against any sibling, but the sibling names supplied are unrelated ice/room-measurement tools, so differentiation is not the binding gap here.

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?

Usage is only implied: 'aus einer vorhandenen reinen Eisprobe' signals the precondition that the sample must be known pure water ice, which frames when the tool applies. There is no explicit statement of when not to use it, no mention of the household-experiment or error-source siblings, and no note on what to do with contaminated or unknown samples.

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