Skip to main content
Glama

getecoback-climate-weather

terrasse_sonnenschutz_vorab_einraeumen_termin

Read-only

Zwei getrennte beschlossene Einräumarbeiten vor einer selbst gesetzten Frist mit nur einer Person koordinieren — Fit two planned shade-item removals into one confirmed attendance window.

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": {
      "anwesend_ab": "<anwesend_ab>",
      "frist": "<frist>",
      "a_min": "<a_min>",
      "b_min": "<b_min>",
      "wechsel_min": "<wechsel_min>",
      "arbeiten_dokumentiert": "<arbeiten_dokumentiert>"
    },
    "name": "terrasse_sonnenschutz_vorab_einraeumen_termin"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_minYesBeobachtete Dauer für erlaubtes Einräumen von Gegenstand A.
b_minYesEntsprechende Dauer für Gegenstand B.
fristYesSelbst vereinbarte Abschlussfrist vor anderen Terminen oder Wetteränderung.
anwesend_abYesFrüheste persönliche Anwesenheit.
wechsel_minYesBeobachtete Zeit zwischen den beiden Arbeitsorten.
arbeiten_dokumentiertYesSind sichere Handhabung laut Anleitung und tatsächliche Anwesenheit für beide Arbeiten geklärt?

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 the safety profile is covered. The description adds useful constraints beyond the schema, namely that only one person is available and the deadline is self-imposed, but it does not explain what the tool returns or how infeasible schedules are handled.

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 definition is a single compact sentence with the core scenario front-loaded. The bilingual German/English repetition is slightly redundant but remains brief and readable.

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 six-parameter planning tool with no output schema, the description covers the input scenario but omits what the tool actually returns. An agent still has to infer whether the result is a schedule, a feasibility check, or a conflict report.

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%, and every parameter already has a German explanation. The description's reference to two removals and one attendance window loosely maps to the duration and timing parameters but adds no syntax, units, or interpretation 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 and resource: coordinate ('koordinieren') two planned shade-item removals ('Einräumarbeiten') within one attendance window. It is clear enough to understand the computation, though it does not explicitly differentiate itself from the many terrasse_* siblings.

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 scenario implies when to use it: two decided removal tasks, one person, and a self-set deadline. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the sibling tools.

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