Skip to main content
Glama

getecoback-raumklima

verschattung_blendpause_zwei_fenster_arbeit

Read-only

Abdeckung gegen zwei beobachtete Blendfenster während einer festen Arbeitszeit planen — Compare observed glare and planned shade in a fixed work 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": {
      "arbeit_ab": "<arbeit_ab>",
      "arbeit_bis": "<arbeit_bis>",
      "blend_a_ab": "<blend_a_ab>",
      "blend_a_bis": "<blend_a_bis>",
      "blend_b_ab": "<blend_b_ab>",
      "blend_b_bis": "<blend_b_bis>",
      "schutz_a_ab": "<schutz_a_ab>",
      "schutz_a_bis": "<schutz_a_bis>",
      "schutz_b_ab": "<schutz_b_ab>",
      "schutz_b_bis": "<schutz_b_bis>"
    },
    "name": "verschattung_blendpause_zwei_fenster_arbeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeit_abYesArbeitsbeginn, Minuten seit Mitternacht.
arbeit_bisYesArbeitsende am selben Tag.
blend_a_abYesBeobachteter Blendbeginn Fenster A.
blend_b_abYesBeobachteter Blendbeginn Fenster B.
blend_a_bisYesBeobachtetes Ende Fenster A.
blend_b_bisYesBeobachtetes Ende Fenster B.
schutz_a_abYesBeginn wirksamer Verschattung an A.
schutz_b_abYesBeginn wirksamer Verschattung an B.
schutz_a_bisYesEnde an A.
schutz_b_bisYesEnde an B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description only says it 'plans' and 'compares' — it does not disclose whether conflicts between Blend- and Schutz-Intervallen are flagged, what is computed, or any constraint such as the windows having to lie within the work period. Little value is added past the annotations.

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 clauses, front-loaded with the German statement followed by an English gloss. The bilingual duplication is slight redundancy but aids comprehension and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A ten-parameter, all-required tool with no output schema needs the description to say what result an agent should expect (e.g. whether shade covers the glare windows, and what conflict indicators appear). Instead the definition stops at 'compare', leaving the outcome and any failure conditions unexplained.

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%, so the schema already documents all ten minute-offset parameters in German. The description adds mild orientation by distinguishing 'observed' glare windows from 'planned' shade, mapping onto the blend_* versus schutz_* parameter families, but gives no extra semantics such as ordering constraints or overlap rules. Baseline 3 applies.

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+resource combination ('Abdeckung ... planen' / 'Compare observed glare and planned shade') scoped to two glare windows inside a fixed work period, which does distinguish it from the many single-window siblings. What the comparison actually yields is left implicit, so it is clear but not fully sharp.

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 phrase 'während einer festen Arbeitszeit' implies the applicable scenario (both windows must fall inside one fixed work period), but there is no explicit when-to-use/when-not statement and no reference to an alternative tool. Guidance is inferred rather than stated.

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