Skip to main content
Glama

getecoback-climate-weather

mietfenster_klebeflaeche_fotodeckung_vor_nach

Read-only

Prüft, welche markierten Klebeflächen nach Abnahme im Fotovergleich tatsächlich abgedeckt sind — Identify matching before-and-after photo coverage of adhesive sites.

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": {
      "markierte_stellen": "<markierte_stellen>",
      "vorher_bilder": "<vorher_bilder>",
      "nachher_bilder": "<nachher_bilder>",
      "bildpaare": "<bildpaare>"
    },
    "name": "mietfenster_klebeflaeche_fotodeckung_vor_nach"
  }
}

Input Schema

NameRequiredDescriptionDefault
bildpaareYesStellen mit beiden vergleichbaren Bildern am selben Ort.
vorher_bilderYesDavon vor Anbringung in vergleichbaren Fotos dokumentiert.
nachher_bilderYesDavon nach Abnahme vergleichbar dokumentiert.
markierte_stellenYesGesamtzahl vorab eindeutig markierter Stellen.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the tool is a comparative check (before/after matching) rather than a listing, but says nothing about what the result contains, whether the counts are validated against each other, or how inconsistency between bildpaare and the other counts is handled.

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 stating what is checked and how, with the bilingual repetition being the only redundancy. Nothing extraneous is included, though the doubled German/English phrasing is slightly wasteful.

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 computation over four required, fully documented numeric parameters with no output schema, the description supplies enough to call it: the comparison basis and the post-removal timing are stated. The main remaining gap is that the shape of the result (counts, ratio, verdict) is never hinted at, which matters when 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% and every parameter already carries a German explanation, so the baseline is 3. The description's terms 'markierte Klebeflaechen', 'nach Abnahme' and 'Fotovergleich' loosely map onto markierte_stellen, nachher_bilder and bildpaare but add no constraint or interpretation the schema lacks, such as whether bildpaare must be <= min(vorher_bilder, nachher_bilder).

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 gives a concrete verb (prueft / 'identify matching') and a specific resource (photo-based coverage of marked adhesive sites before vs. after removal). Given that the tool name is an opaque German compound, this is doing real work. It does not, however, contrast itself with any of the numerous vor/nach siblings, so the agent must infer the distinction.

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?

Usage is only implied: 'nach Abnahme' and 'Fotovergleich' suggest this is a post-removal verification step using paired photos. There is no explicit statement of when to call this instead of a sibling such as fensterplatte_markierungen_nach_abnahme, and no prerequisites or exclusions are given.

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