Skip to main content
Glama

getecoback-climate-weather

feuchtegranulat_nachfuellkosten

Read-only

Nachfüllkosten eines passiven Granulatbehälters aus der eigenen Standzeit abschätzen — Estimate refill consumption and cost from observed service life.

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": {
      "refill_eur": "<refill_eur>",
      "observed_weeks": "<observed_weeks>",
      "planned_weeks": "<planned_weeks>",
      "containers": "<containers>"
    },
    "name": "feuchtegranulat_nachfuellkosten"
  }
}

Input Schema

NameRequiredDescriptionDefault
containersYesGleichartig genutzte Behälter.
refill_eurYesPreis eines einzelnen Nachfüllsatzes in Euro.
planned_weeksYesGeplanter Nutzungszeitraum in Wochen.
observed_weeksYesEigene Standzeit in Wochen pro Nachfüllsatz.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's added signal is that the result is an estimate ('abschätzen' / 'Estimate'), i.e. a pure computation rather than a measurement. It says nothing about assumptions, rounding, or what happens at the parameter bounds.

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?

Two short sentences, front-loaded with the German verb phrase, and the English restatement aids clarity rather than bloat. It is efficiently sized for a simple calculator, though the bilingual duplication is mildly redundant.

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 four-parameter, single-formula calculator with no output schema, the description is workable but leaves the agent guessing what the result represents (total cost over the planned period? cost per week? consumption quantity?). Since no output schema exists, some explanation of the returned figures would have been valuable.

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 four parameters already carry their own German documentation with min/max bounds. The description adds only a loose mapping of 'observed service life' to observed weeks and 'consumption and cost' to the refill inputs; it introduces no units, edge-case behavior, or interaction between parameters 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 names a concrete verb and resource: estimating ('abschätzen') refill consumption and cost for a passive granulate container, derived from observed service life. That is far more specific than the tool name alone would convey, though it never positions itself against any sibling tool.

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 der eigenen Standzeit' signals that the caller must supply their own measured service life, which hints at the data prerequisite. There is no explicit statement of when to reach for this instead of a related calculation tool, and no stated preconditions or exclusions.

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