Skip to main content
Glama

getecoback-climate-weather

terrasse_abendsonne_blickrichtung_probe

Read-only

Zwei beobachtete Terrassenanordnungen auf Blendung bei verschiedenen Blickrichtungen prüfen — Compare glare by facing direction, not just the overall shadow area.

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_blick_zum_tisch": "<a_blick_zum_tisch>",
      "a_blick_nach_vorn": "<a_blick_nach_vorn>",
      "b_blick_zum_tisch": "<b_blick_zum_tisch>",
      "b_blick_nach_vorn": "<b_blick_nach_vorn>",
      "gleiche_abendlage": "<gleiche_abendlage>"
    },
    "name": "terrasse_abendsonne_blickrichtung_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_blick_nach_vornYesWar der übliche Blick nach vorn in A ausreichend blendfrei?
a_blick_zum_tischYesWar der Blick zur eigenen Tischfläche in A ausreichend blendfrei?
b_blick_nach_vornYesEntsprechende Beobachtung B nach vorn.
b_blick_zum_tischYesEntsprechende eigene Beobachtung B am Tisch.
gleiche_abendlageYesWaren Tageszeit, Himmel und Beobachtungsposition mit der geplanten Abendlage vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add meaning. It adds the comparative, directional framing, but does not state what the probe produces (a verdict, a ranking, a pass/fail) despite having no output schema to rely on. That is a meaningful gap for a tool whose whole value is the resulting comparison.

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 compact statement with the core idea front-loaded and followed by the contrastive qualifier. The German and English halves convey the same content, so the second clause is partly duplicative, but the overall length is well within bounds.

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

Completeness4/5

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

For a read-only probe with five fully described required booleans, the description supplies enough to call the tool correctly, and the annotations cover the safety profile. The remaining shortfall is that no return behavior is indicated, which matters slightly more given there is no output schema.

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%, with each of the five booleans individually documented, so the schema does the heavy lifting and a baseline 3 applies. The description adds nothing about the parameters and does not surface the important precondition embedded in 'gleiche_abendlage' (comparable time, sky, and observer position) as a validity condition for the comparison.

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 operation (compare two observed terrace arrangements for glare) and a specific dimension of comparison (facing direction rather than overall shadow area), which lets an agent distinguish it from area-based shadow siblings. It stops short of naming any sibling tool explicitly, so the differentiation is conceptual rather than definitive.

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 clause 'Compare glare by facing direction, not just the overall shadow area' implies when this probe is the right choice (directional glare assessment rather than total shaded area), but there is no explicit statement of prerequisites such as having already observed two arrangements, nor any when-not guidance. Usage must be inferred from the purpose statement.

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