Skip to main content
Glama

getecoback-raumklima

kontaktgrill_signaltyp_zeitplan

Read-only

Klären, welche Anzeige ein geplantes Minutenprotokoll tragen kann — Distinguish a documented countdown from a qualitative grill-stage display.

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": {
      "variante": "<variante>",
      "minutenwerte_noetig": "<minutenwerte_noetig>",
      "unabhaengiger_timer": "<unabhaengiger_timer>"
    },
    "name": "kontaktgrill_signaltyp_zeitplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
varianteYesBestätigte Tefal-Referenz am Typenschild.
minutenwerte_noetigYesDer Ablaufplan braucht numerische Restminuten statt reiner Stufenkennzeichnung.
unabhaengiger_timerYesEin unabhängiger Timer steht zur Erfassung des eigenen Zeitplans zur Verfügung.

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 establish readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds that this is a clarification/decision about display capability and the countdown-vs-stage distinction, but it does not describe the response format or how the determination is produced.

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?

It is a single, front-loaded sentence with no filler. The German/English restatement is slightly redundant, which keeps it from being maximally tight.

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 three-parameter decision helper with no output schema, the description gives the decision context but not the expected result shape or how the parameters combine into an answer. It is adequate at a high level but leaves the agent guessing about output semantics.

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 coverage is 100% and all three parameters, including the variante enum, are documented in the schema. The description echoes the conceptual distinction behind minutenwerte_noetig but adds no per-parameter syntax, defaults, or combination rules 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 determination: which display can carry a planned minute protocol, and explicitly frames the distinction as documented countdown versus qualitative grill-stage display. It does not name sibling tools or contrast with them, so it is clear but not sibling-differentiated.

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?

The planned-minute-protocol context implies when the tool is relevant, but there is no explicit 'use this when' or 'do not use' guidance and no named alternative. An agent must infer usage from the purpose statement.

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