Skip to main content
Glama

getecoback-climate-weather

gebraucht_kondensatspur_vor_nach_stillstand

Read-only

Bei bereits ausgeschaltetem Gerät eine äußerlich beobachtete Spur nach Lage und Wiederauftreten dokumentieren — Separate previously visible marks from an observed recurrence while idle.

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": {
      "gleiches_exemplar_und_untergrund": "<gleiches_exemplar_und_untergrund>",
      "trocken_beobachtet": "<trocken_beobachtet>",
      "neu_sichtbar": "<neu_sichtbar>",
      "andere_wasserquelle_offen": "<andere_wasserquelle_offen>"
    },
    "name": "gebraucht_kondensatspur_vor_nach_stillstand"
  }
}

Input Schema

NameRequiredDescriptionDefault
neu_sichtbarYesWurde später am markierten Bereich erneut Wasser beobachtet?
trocken_beobachtetYesWurde der markierte Bereich zwischen den Beobachtungen tatsächlich trocken gesehen?
andere_wasserquelle_offenYesKommt nach den vorhandenen Beobachtungen eine andere Wasserquelle infrage?
gleiches_exemplar_und_untergrundYesGehören Zeitpunkte, Bodenstelle und Gerät eindeutig zusammen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, closed-world operation. The description adds useful domain context about the device being off and separating prior visible marks from an observed recurrence, but it does not describe the output or how the observation is recorded.

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 a single, front-loaded sentence with no procedural filler. The German/English bilingual restatement is useful but slightly duplicative, which keeps it below maximum conciseness.

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 a read-only tool with four fully documented required booleans and no output schema, the description gives enough context to understand the scenario. However, it does not clarify what documentation or decision results from the inputs, and it omits details such as the 'gebraucht' scope present in the tool name.

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 100% description coverage, so all four booleans are already well explained. The description frames the overall observation task and recurrence distinction, but it adds little parameter-specific meaning beyond the schema.

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 names a specific action (documenting an externally observed trace), a specific condition (device already switched off), and the distinction to capture between earlier marks and recurrence during idle. The tool's scope is clear, though it does not explicitly route the agent away from any sibling.

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?

The precondition 'bei bereits ausgeschaltetem Gerät' implies when the tool applies, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative. Usage is reasonably inferable but not directly instructed.

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