Skip to main content
Glama

getecoback-climate-weather

camper_absorber_rueckkehr_vor_offener_besuchspause

Read-only

Prüfe, ob eine belegte Kontrollfrist vor dem nächsten bestätigten Zugang endet — Match a documented absorber check deadline against actual access

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": {
      "letzter_check_tag": "<letzter_check_tag>",
      "kontrollfrist_tage": "<kontrollfrist_tage>",
      "naechster_tag": "<naechster_tag>",
      "zugang_zugesagt": "<zugang_zugesagt>"
    },
    "name": "camper_absorber_rueckkehr_vor_offener_besuchspause"
  }
}

Input Schema

NameRequiredDescriptionDefault
naechster_tagYesFrühester bestätigter Zugang zum abgestellten Fahrzeug
zugang_zugesagtYesDer nächste Zugang ist tatsächlich zugesagt und erlaubt die Kontrolle des betreffenden Bereichs
letzter_check_tagYesTag der jüngsten tatsächlich dokumentierten Kontrolle
kontrollfrist_tageYesZuvor festgelegter Abstand bis zur Kontrolle, gestützt auf eigene Beobachtung oder Produktunterlage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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, and the description's 'Prüfe'/'Match' framing is consistent with a safe read. Beyond that it adds little behavioral context: it does not say what the check returns (the implied boolean outcome), how the zugang_zugesagt flag affects the result, or how edge cases (deadline exactly equal to access day) are treated.

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 condition stated before the gloss; nothing is wasted. The bilingual echo is mildly redundant but useful for disambiguation, keeping it just short of maximum.

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 simple four-parameter comparison tool with a fully documented schema, the description covers the concept adequately. However, with no output schema and no statement of the return value or how to interpret a true/false result, an agent cannot know what a successful call yields.

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%, so all four parameters are already documented in the schema, which sets the baseline at 3. The description gestures at the two conceptual inputs (Kontrollfrist, Zugang) but adds no format, ordering, or edge-case meaning beyond what the schema provides.

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 operation (check whether a documented control deadline ends before the next confirmed access) with a clear verb ('Prüfe'/'Match') and two concrete resources (Kontrollfrist vs. Zugang). The domain jargon makes it harder to parse than a plain-language statement, but the core comparison is unambiguous and not a restatement of the tool name.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The description states what the check is but never tells an agent in which situation to call it rather than one of the many sibling 'rueckkehr'/'kontrolle' tools, and no alternatives are named.

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