Skip to main content
Glama

getecoback-climate-weather

wasserprobe_gefaesswaage_tarawechsel

Read-only

Zwei Auffangstände trotz verschiedener Gefäßgewichte in reine Wassermassen umrechnen — Compare two water-only masses with different recorded vessel tares.

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": {
      "a_voll_g": "<a_voll_g>",
      "a_leer_g": "<a_leer_g>",
      "b_voll_g": "<b_voll_g>",
      "b_leer_g": "<b_leer_g>",
      "inhalt_wasser_und_waage_gleich": "<inhalt_wasser_und_waage_gleich>"
    },
    "name": "wasserprobe_gefaesswaage_tarawechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_leer_gYesTrockene Leermasse genau dieses Gefäßes.
a_voll_gYesBruttomasse des ersten Sammelgefäßes in Gramm.
b_leer_gYesTrockene Leermasse des zweiten Gefäßes.
b_voll_gYesBruttomasse des zweiten Sammelgefäßes.
inhalt_wasser_und_waage_gleichYesEnthielten beide nur das beobachtete Wasser, auf derselben Waage gemessen?

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 establish that this is a read-only, closed-world calculation, and the description adds that gross readings are reduced to water-only masses for comparison. However, it does not explain the result shape, what happens when the shared-scale/water-only boolean is false, or any error behavior.

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?

The description is compact and front-loaded, with the core operation stated immediately. The bilingual repetition is slightly redundant but still efficient.

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 five-parameter calculation tool with no output schema, the description should explain what result is returned and the role of the required boolean precondition. It gives the purpose adequately but leaves the output and failure semantics undocumented.

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?

The input schema has full description coverage for all five parameters, so the schema already defines each gross, tare, and boolean field clearly. The description reinforces the tare-subtraction concept but adds no parameter-level meaning beyond the schema.

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 states a specific operation: converting two gross vessel readings with different tares into water-only masses and comparing them. It is clear what the tool does, though it does not explicitly differentiate itself from any named sibling alternative.

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 implied by the scenario of two different recorded vessel tares, but the description gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent can infer the situation but must rely on the parameter names for confirmation.

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