Skip to main content
Glama

getecoback-climate-weather

infrarot_sichtlinie_arbeitsplatz

Read-only

Mögliche Abschattung der Strahlungsfläche zu einem Sitzplatz anhand der Sichtlinie einordnen — Check an unobstructed line of sight for radiant heating placement.

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": {
      "freie_sichtlinie": "<freie_sichtlinie>",
      "montageart": "<montageart>",
      "laut_handbuch_geprueft": "<laut_handbuch_geprueft>"
    },
    "name": "infrarot_sichtlinie_arbeitsplatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
montageartYesLaut Modellanleitung vorgesehene Position.
freie_sichtlinieYesSichtlinie vom vorgesehenen Sitzplatz zur Heizfläche ohne Möbel, Textilien oder andere größere Hindernisse?
laut_handbuch_geprueftYesVom Hersteller vorgeschriebene Montageposition und Abstände geprüft?

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 mark this as a read-only, closed-world check. The description adds the purpose of classifying possible shading, but it does not explain how the sightline inputs are evaluated, what the assessment returns, or any limitations. With annotation coverage, this is adequate but thin.

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 front-loaded sentence with no filler. The German and English clauses duplicate the same meaning, so it is efficient but not perfectly lean.

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 simple three-input read-only assessment with full schema coverage and annotations, the core check is stated. However, since there is no output schema, the description does not say what the assessment result looks like or how the inputs drive it, leaving a gap.

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% for all three parameters, including the enum and parameter descriptions. The description reinforces the 'Sichtlinie' concept but adds no interpretation beyond the schema for montageart or laut_handbuch_geprueft.

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 states a specific action (einordnen/check) and resource: possible shading of the radiant surface relative to a seat via the line of sight, for radiant heating placement. It is clearly more than a restatement of the name, but it does not explicitly distinguish this check from sibling tools.

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 'for radiant heating placement' implies the usage scenario, but there is no explicit instruction on when to call this tool versus alternatives, no prerequisites, and no when-not guidance. The guidance is therefore only implied.

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