Skip to main content
Glama

getecoback-raumklima

sonnenschutz_system_gwert_vergleichen

Read-only

Zwei deklarierte Gesamtenergiedurchlassgrade nur bei passender Verglasung vergleichen — Compare glazing-and-shade g-tot values at equivalent rating conditions.

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": {
      "alt_g_tot": "<alt_g_tot>",
      "neu_g_tot": "<neu_g_tot>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "sonnenschutz_system_gwert_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_g_totYesAnteil durchgelassener Sonnenenergie für das alte System, 0 bis 1.
neu_g_totYesEntsprechende Angabe für das vorgesehene System, 0 bis 1.
vergleichbarYesFür beide stehen kombinierte g-tot-Werte für dieselbe Verglasung und vergleichbare Prüfbedingungen bereit?

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 safety profile is covered. The description adds that only *declared* values may be compared and only under matching glazing/rating conditions, which is useful context. It says nothing about what the comparison returns or what happens when the systems are not comparable, leaving that behavior undisclosed.

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 constraint placed before the action, which is the right ordering. The German-English duplication adds length without new information, so it is efficient but not maximally tight.

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 three parameters are required and fully described in the schema, and the annotation covers the read-only nature. However, with no output schema, the description gives no indication of what the comparison yields (a delta, a verdict, a recommendation), leaving the result shape to guesswork.

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 three parameters documented including ranges and the comparability gate. The description adds only a restatement of the comparability condition, not format, units, or edge-case handling beyond the schema. 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?

States a specific verb (vergleichen / compare) and resource (Gesamtenergiedurchlassgrade / g-tot values of glazing-plus-shade systems), so an agent knows this is a value-comparison tool rather than a measurement or lookup. It does not name or differentiate itself from any sibling, which keeps it from a 5.

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

Usage Guidelines4/5

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

The clause 'nur bei passender Verglasung' / 'at equivalent rating conditions' gives a clear precondition for legitimate use. It does not name alternatives or state what to do when the precondition fails, so no explicit routing or exclusion is provided.

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