Skip to main content
Glama

getecoback-climate-weather

auto_parkprobe_sonnenschutz_zeitversatz_am_selben_platz

Read-only

Trenne die dokumentierte Zeit ohne aufgelegten Sonnenschutz von der anschließenden geschützten Phase — Separate unprotected and protected time in a parked sunshade trial

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": {
      "standbeginn_min": "<standbeginn_min>",
      "schutz_aufgelegt_min": "<schutz_aufgelegt_min>",
      "erste_flaechenmessung_min": "<erste_flaechenmessung_min>",
      "zweite_flaechenmessung_min": "<zweite_flaechenmessung_min>",
      "ausrichtung_unveraendert": "<ausrichtung_unveraendert>"
    },
    "name": "auto_parkprobe_sonnenschutz_zeitversatz_am_selben_platz"
  }
}

Input Schema

NameRequiredDescriptionDefault
standbeginn_minYesBeginn der bestätigten unbewegten Parkphase
schutz_aufgelegt_minYesErste Minute mit belegter Schutzposition an der Frontscheibe
ausrichtung_unveraendertYesFahrzeug und Messpunkt befinden sich während der Probe unverändert am selben Ort
erste_flaechenmessung_minYesMinute der frühen Temperaturablesung am Lenkrad
zweite_flaechenmessung_minYesMinute der späteren Ablesung am gleichen Punkt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. Beyond that the description adds nothing: it does not say what the split produces (durations, intervals, labeled segments), whether the measurement minutes must fall inside the respective phases, or how the 'ausrichtung_unveraendert' flag is enforced. For a pure computation tool with no output schema, this is a real gap.

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 core operation stated first; the German/English duplication adds a little redundancy but no filler or hedging.

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 five required numeric parameters, a boolean guard, and no output schema, the definition should at least sketch what is returned (e.g. protected vs. unprotected durations) and any ordering preconditions. Annotations cover the read-only nature, but the return shape and validation behavior remain 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 description coverage is 100%, so the schema already explains each parameter. The description only implies that schutz_aufgelegt_min is the split point between the two phases, which adds mild meaning but no detail on ordering constraints or how the two Flächenmessung minutes relate to the phases. 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 specific verb ('trenne/separate') and the resource being separated ('dokumentierte Zeit ohne aufgelegten Sonnenschutz' vs. 'anschließende geschützte Phase'), so an agent can tell this partitions a timeline at the moment shade was applied. It stops short of naming how it differs from shade-related siblings like sonnenschutz_scheibe_und_platz_reagieren_getrennt, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the many sibling shade/ventilation tools, no prerequisites (e.g. that the two phase boundaries must be ordered), and no exclusions. Usage must be inferred entirely from the name and description.

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