Skip to main content
Glama

getecoback-raumklima

balkon_sonnenschutz_mietuebergabe_zustandsbelege

Read-only

Beim Abnehmen genutzten Sonnenschutzes fehlende Zustandsbelege je Balkonbereich erfassen — Identify the missing before-and-after record for a reversible balcony setup.

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": {
      "vor_boden": "<vor_boden>",
      "nach_boden": "<nach_boden>",
      "vor_gelaender": "<vor_gelaender>",
      "nach_gelaender": "<nach_gelaender>",
      "gleiches_aufmass": "<gleiches_aufmass>"
    },
    "name": "balkon_sonnenschutz_mietuebergabe_zustandsbelege"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_bodenYesGibt es eine vergleichbare Vorheraufnahme der genutzten Bodenstelle?
nach_bodenYesGibt es die Nachheraufnahme derselben Bodenstelle?
vor_gelaenderYesGibt es eine Vorheraufnahme des beteiligten Geländerbereichs?
nach_gelaenderYesGibt es die Nachheraufnahme desselben Geländerbereichs?
gleiches_aufmassYesSind Stellen, Ansichten und Umfang der Übergabe bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already define the tool as safe (readOnlyHint:true), setting the primary behavioral constraint. The description adds the logical intent—identifying gaps—but does not elaborate on return values or operational behavior beyond the boolean schema.

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 brief and highly focused. Although the mix of German and English is present, the two sentences convey the necessary domain context with minimal wasted language.

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?

Given the complexity is defined by 5 highly specific boolean checks, the description successfully provides the necessary overarching narrative (missing records during removal) required for an agent to utilize the tool correctly in a handover context.

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?

Since the schema provides 100% coverage with detailed descriptions for each parameter, the description merely adds the high-level conceptual meaning (i.e., these are 'before' and 'after' captures for 'floor' and 'railing'). This meets the baseline standard when the schema is complete.

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

Purpose5/5

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

The description clearly states the goal: capturing missing state records (Zustandsbelege) specifically during the removal of used sun protection (Sonnenschutz) on a balcony.

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?

It provides critical context by specifying that the tool is for a 'reversible balcony setup,' helping the agent identify the correct scenario for its use and distinguishing it from general maintenance 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