Skip to main content
Glama

getecoback-climate-weather

hitze_vorbereitung_vorlauf_abhaengige_schritte

Read-only

Vor erwartetem Sonneneintrag Zeitreserve für nacheinander auszuführende Vorbereitungen bestimmen — Check a two-step shading preparation sequence against an expected heat onset.

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": {
      "bis_sonneneintrag_min": "<bis_sonneneintrag_min>",
      "verschattung_bereit_min": "<verschattung_bereit_min>",
      "kontrolle_min": "<kontrolle_min>",
      "gewuenschte_reserve_min": "<gewuenschte_reserve_min>"
    },
    "name": "hitze_vorbereitung_vorlauf_abhaengige_schritte"
  }
}

Input Schema

NameRequiredDescriptionDefault
kontrolle_minYesNachfolgende Kontrolle von Zustand und Fensterstellung.
bis_sonneneintrag_minYesZeit bis zur erwarteten direkten Sonne am betrachteten Fenster.
gewuenschte_reserve_minYesEigener Zeitpuffer vor dem erwarteten Sonneneintrag.
verschattung_bereit_minYesEigenes gemessenes Zeitfenster, um vorhandenen Sonnenschutz vorzubereiten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 side-effect-free, closed-world computation. The description adds the useful model that the two preparation steps run sequentially ("nacheinander auszuführen"), but it never says what the check yields (sufficient/insufficient reserve, slack minutes, recommended start) and no output schema exists to cover that gap.

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

Conciseness5/5

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

A single front-loaded sentence with a bilingual gloss; the scenario constraint comes first and nothing is wasted. There is no filler, hedging, or repetition of schema content.

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 parameters are required, the tool is a pure read-only calculation with no output schema, and the description conveys the underlying time-budget model well enough to call it. What remains missing is the shape of the answer — what the agent should expect back and how to interpret it — which matters for a check-style tool with no documented return value.

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 description coverage is 100%, so the baseline would be 3; the description earns an extra point by explaining how the four numbers relate — two sequential preparation durations (readiness plus control) are compared against time-to-sun plus a desired buffer. That sequencing semantic is not obvious from the four independent numeric fields alone.

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 pairs a specific verb ("Zeitreserve ... bestimmen" / "check") with a concrete domain object: a two-step shading preparation sequence compared against an expected heat onset. An agent can tell this is a time-budget feasibility calculation, not a data lookup. It stops short of naming any sibling or contrasting itself with the other heat-planning tools, so it is clear but not differentiating.

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?

"Vor erwartetem Sonneneintrag" and the mention of a two-step preparation sequence imply the scenario in which this applies, so usage is inferable. However, there is no explicit when-to-use/when-not guidance, no statement of prerequisites, and no pointer to an alternative tool for simpler single-step checks.

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