Skip to main content
Glama

getecoback-raumklima

backofen_zwei_teams_praxisreservierung_prioritaet

Read-only

Beim bereits gemeinsam bestätigten Backofenbetrieb eine gleichrangige Doppelbuchung mit der vereinbarten Vorrangregel lösen — Resolve an oven booking tie by the household’s explicit turn-taking rule.

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_bestaetigt": "<a_bestaetigt>",
      "b_bestaetigt": "<b_bestaetigt>",
      "letzter_vorrang": "<letzter_vorrang>",
      "beide_passen_gleichzeitig": "<beide_passen_gleichzeitig>"
    },
    "name": "backofen_zwei_teams_praxisreservierung_prioritaet"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_bestaetigtYesAufgabe A ist mit dokumentiert geeignetem Betrieb angemeldet.
b_bestaetigtYesAufgabe B ist mit dokumentiert geeignetem Betrieb angemeldet.
letzter_vorrangYesWer bekam beim letzten gleichrangigen Konflikt Vorrang?
beide_passen_gleichzeitigYesFür diese Aufgaben ist eine gleichzeitige Belegung ausdrücklich geprüft und akzeptiert.

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, and the description is consistent with a pure decision operation. It adds useful context that the rule must be the household's explicit agreed rule, but it never says what the resolution yields (which side wins, or a tie verdict) despite having 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.

Conciseness4/5

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

A single front-loaded sentence with the condition before the action; the German/English pairing is redundant but compact and does not obscure the core meaning.

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?

With four required parameters fully documented and safety covered by annotations, the main missing piece is the result contract — what the tool returns when the rule resolves a tie versus when it cannot. For a resolution tool with no output schema, that is a meaningful 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 coverage is 100% with all four parameters individually described, so the schema carries the semantics. The description reinforces that 'letzter_vorrang' represents the agreed precedence rule, but adds no format or edge-case guidance 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 gives a specific verb ('lösen'/'Resolve') and a precise resource ('gleichrangige Doppelbuchung' / 'oven booking tie'), plus the scope condition that the oven operation is already jointly confirmed. It is clearly a tie-break computation rather than a booking or mutation, though it does not explicitly name a sibling it differs from.

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 through preconditions: both tasks confirmed, equal rank, and an agreed precedence rule. It does not state when NOT to use it or point to any alternative sibling tool for non-tied or non-confirmed cases, leaving the agent to infer the boundary.

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