Skip to main content
Glama

getecoback-raumklima

sitzplaetze_beobachtete_schattenzone

Read-only

Zwei Sitzpositionen mit den Grenzen eines am Boden beobachteten Schattenflecks abgleichen — Classify two candidate seating positions in a marked rectangular patch of shade.

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": {
      "schatten_links_cm": "<schatten_links_cm>",
      "schatten_rechts_cm": "<schatten_rechts_cm>",
      "schatten_vorn_cm": "<schatten_vorn_cm>",
      "schatten_hinten_cm": "<schatten_hinten_cm>",
      "platz_a_x_cm": "<platz_a_x_cm>",
      "platz_a_y_cm": "<platz_a_y_cm>",
      "platz_b_x_cm": "<platz_b_x_cm>",
      "platz_b_y_cm": "<platz_b_y_cm>"
    },
    "name": "sitzplaetze_beobachtete_schattenzone"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_a_x_cmYesErste Koordinate des markierten Platzes A.
platz_a_y_cmYesZweite Koordinate von A.
platz_b_x_cmYesErste Koordinate des markierten Platzes B.
platz_b_y_cmYesZweite Koordinate von B.
schatten_vorn_cmYesVordere Grenze auf der rechtwinkligen Skizzenachse.
schatten_links_cmYesLinke Grenze des momentan beobachteten Schatten-Rechtecks.
schatten_hinten_cmYesHintere Grenze.
schatten_rechts_cmYesRechte Grenze des Rechtecks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that the tool is read-only and closed-world, so the safety profile is supplied externally. The description adds that the comparison uses boundaries of an observed ground shadow patch and classifies two candidate positions, but it does not explain the classification result, boundary handling, or assumptions about coordinates.

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 short and front-loads the core action and resource. The bilingual phrasing is somewhat redundant for an agent, but it remains efficient and does not bury the purpose in extra prose.

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 an eight-parameter geometric classification tool with no output schema, the description gives enough context to understand the basic operation. However, it does not describe what the classification returns or how the two positions are evaluated, leaving an important gap for correct invocation and interpretation.

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?

The input schema has full description coverage for all eight parameters, so the schema already defines each coordinate and boundary. The description adds no parameter-level meaning beyond what the schema provides, which fits the baseline-3 case for high schema coverage.

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 clearly states a specific verb and resource: comparing two seating positions against the boundaries of an observed rectangular shadow patch, with a classification goal. It is distinguishable from siblings by its focus on two candidate positions and a marked ground shadow rectangle, though it does not explicitly contrast itself with related shadow or seating tools.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and it names no alternatives. The use case is implied by the classification wording, but an agent is not told when this tool should be selected over related sibling tools.

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