Skip to main content
Glama

getecoback-raumklima

kuechenwaage_tara_behaelterwechsel_charge

Read-only

Die getrennten Tara-Werte zweier Küchenbehälter bei einer Umfüllprobe berücksichtigen — Track material transfer using separate container tare weights.

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": {
      "behaelter_a_g": "<behaelter_a_g>",
      "a_mit_inhalt_g": "<a_mit_inhalt_g>",
      "behaelter_b_g": "<behaelter_b_g>",
      "b_mit_inhalt_g": "<b_mit_inhalt_g>",
      "rest_a_g": "<rest_a_g>"
    },
    "name": "kuechenwaage_tara_behaelterwechsel_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
rest_a_gYesNach dem Umfüllen separat beobachteter Inhaltsrest in A.
behaelter_a_gYesGeleerter Behälter A in Gramm.
behaelter_b_gYesGeleerter Behälter B in Gramm.
a_mit_inhalt_gYesBruttogewicht A vor dem Umfüllen.
b_mit_inhalt_gYesBruttogewicht B nach dem Umfüllen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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. The description adds some domain context (two containers, transfer test, separate tare weights) but does not explain what the tool computes or returns, which is the core behavior for a calculation-style tool. With annotations present, a 3 is appropriate for the modest added context.

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 two short sentences (German and English translation) with no wasted words. It is front-loaded with the German statement, though the bilingual duplication may be redundant for a single-language agent. Overall it is efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has five required numeric parameters and no output schema, so the description should explain what the tool computes or returns. Instead, it only restates the domain (tare weights of two containers) without clarifying the calculation or expected result. For a read-only calculation tool, this leaves a significant functional gap.

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 the schema fully documents all five parameters in German. The description adds no parameter-level meaning beyond what the schema provides (e.g., it does not clarify how rest_a_g relates to the transfer calculation). Baseline 3 is correct 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (tare values of two kitchen containers during a transfer test) but the action is vague: 'berücksichtigen'/'track' does not specify whether the tool calculates net transfer, records values, or something else. It is not a tautology, but it lacks a precise verb and does not distinguish this tool from the many sibling task-specific tools.

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?

There is no when-to-use guidance, no conditions for selecting this tool over alternatives, and no mention of prerequisites or exclusions. The description only states the domain context, leaving the agent to infer usage entirely.

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