Skip to main content
Glama

getecoback-climate-weather

kontaktgrill_haeufigkeit_auffangbehaelter_protokoll

Read-only

Reinigungspausen für wiederholte Grillrunden mit dem eigenen Protokoll abschätzen — Estimate when recorded runoff would reach a chosen manual-compatible service point.

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": {
      "grenze_ml": "<grenze_ml>",
      "start_ml": "<start_ml>",
      "max_je_runde_ml": "<max_je_runde_ml>",
      "szenario_geprueft": "<szenario_geprueft>"
    },
    "name": "kontaktgrill_haeufigkeit_auffangbehaelter_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
start_mlYesBeobachteter Behälterinhalt vor dem vorgesehenen Block.
grenze_mlYesZulässiger Pflegepunkt der Auffangschale, als Menge eingegeben.
max_je_runde_mlYesGrößter protokollierter Zuwachs unter vergleichbaren Bedingungen.
szenario_geprueftYesHerstellervorgaben zu Auffangbehälter und Pflege sind für den vorgesehenen Ablauf geklärt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 agent knows this is a closed, side-effect-free computation. The description adds that the estimate is grounded in 'recorded' protocol values and must be 'manual-compatible', which is useful context. It never says what the response contains (a round count? a volume? a timestamp), which is a real gap for a tool with no output schema.

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

Conciseness3/5

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

It is a single short sentence, but the German and English halves are paraphrases of each other rather than complementary detail, so roughly half the text is redundant. The core intent is front-loaded, but the dense bilingual phrasing ('manual-compatible service point') costs clarity without adding information.

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?

All four required parameters are fully documented in the schema and the operation is a simple read-only estimate, so the definition is broadly sufficient. However, with no output schema, the description should state what is returned and how the estimate is expressed; without that an agent must guess at the result shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description slightly improves on it by framing the parameters as a coherent model: 'recorded runoff' ties to start_ml/max_je_runde_ml and 'manual-compatible service point' ties to grenze_ml, clarifying that the limit is a specified care point rather than an arbitrary threshold. It does not add units or edge-case semantics, so it stays below 5.

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 German clause names an intent (estimating cleaning intervals for repeated grill rounds) and the English gloss narrows it to when recorded runoff reaches a chosen service point. It is understandable but hedged: 'Reinigungspausen abschätzen' does not quite match the arithmetic the parameters imply (rounds until grenze_ml is reached), and no sibling such as kontaktgrill_pflegegruppe_abtropfplatz is named to sharpen the boundary.

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 explicit when-to-use or when-not-to-use guidance and no named alternative among the many kontaktgrill_* siblings. The only usage signal is indirect — the required szenario_geprueft flag implies manufacturer specs must already be clarified before calling — but the description never states this as a precondition.

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