Skip to main content
Glama

getecoback-climate-weather

sonnenschutzfolie_glasfreigabe

Read-only

Vor dem Kauf einer Sonnenschutzfolie Glasaufbau und Herstellerfreigabe abgleichen — Screen glazing and installation-side evidence for a solar film.

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": {
      "glasaufbau_bekannt": "<glasaufbau_bekannt>",
      "seite": "<seite>",
      "freigabe": "<freigabe>"
    },
    "name": "sonnenschutzfolie_glasfreigabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
seiteYesVorgesehene Seite.
freigabeYesSchriftlicher Abgleich des konkreten Folienprodukts mit Glasaufbau und Montageseite?
glasaufbau_bekanntYesAufbau, Beschichtung und Scheibentyp identifiziert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 no behavioral detail: it does not say what happens when 'freigabe' is 'nein' or 'unbekannt', whether a negative result blocks a purchase, or what evidence the agent should expect back. With a 3-parameter read tool and no output schema, this is a notable gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence plus an English gloss, which is compact and puts the gating condition first. The bilingual echo ('Screen glazing and installation-side evidence for a solar film') mostly repeats the German clause without new information, so a portion of the text does not earn its place.

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

Completeness2/5

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

There is no output schema, and the annotations only cover read-only/local status, so the description must explain the return semantics of this verification check. It does not say whether missing or unknown evidence yields a warning, a refusal, or a pass, leaving the agent unable to predict outcomes for its three required inputs.

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% and two of three parameters carry enums, so the schema fully documents inputs. The description restates the concepts (Glasaufbau, Freigabe, Montageseite) without adding format, weighting, or interpretation guidance beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific domain action, comparing glazing build-up and manufacturer approval before buying a solar film, but it never says what the tool actually produces (a verdict, a warning, a checklist?) or what the resource returned is. An agent knows the topic area but not the operation's result, so it is vague rather than tautological.

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?

'Vor dem Kauf einer Sonnenschutzfolie' gives a clear timing cue that implies when the tool applies. However, no alternative tool or exclusion is named, and nothing tells the agent when this check is unnecessary (e.g. already-verified film). Usage is implied rather than stated.

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