Skip to main content
Glama

getecoback-climate-weather

gebrauchtgeraet_fotos_nach_letzter_aenderung

Read-only

Vorliegende Fotos auf den Zustand nach der zuletzt genannten Änderung begrenzen — Separate usable current pictures from pre-change images.

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": {
      "objekt_belegt": "<objekt_belegt>",
      "letzter_eingriff_tag": "<letzter_eingriff_tag>",
      "foto_front_tag": "<foto_front_tag>",
      "foto_zugang_tag": "<foto_zugang_tag>",
      "uhrzeit_gleichentag": "<uhrzeit_gleichentag>"
    },
    "name": "gebrauchtgeraet_fotos_nach_letzter_aenderung"
  }
}

Input Schema

NameRequiredDescriptionDefault
objekt_belegtYesZeigen die Fotos nachweislich genau das angebotene Exemplar?
foto_front_tagYesBekannter Aufnahmetag der Front.
foto_zugang_tagYesBekannter Aufnahmetag des zugänglichen Prüfbereichs.
uhrzeit_gleichentagYesIst bei Gleichstand am Änderungstag die Aufnahme nach der Änderung eindeutig belegt?
letzter_eingriff_tagYesTag der letzten für den Zustand relevanten Änderung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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. The description adds nothing further: it does not reveal the return shape, how the comparison is decided when the change day equals the photo day, or what happens with photos whose date is unproven. For a read-only decision tool driven by five boolean/day inputs, that is a real 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?

The definition is short and front-loaded, but the German and English sentences largely restate each other rather than complementing one another, so half the text is redundant. No structural cues (bullets, conditions) are given for a tool that clearly has conditional logic.

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?

With five required parameters, no output schema, and no annotations covering logic, the description should explain the decision rule and the return value. It does neither, leaving the agent unable to predict what calling it yields beyond a vague 'separation' of images.

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 five parameters (objekt_belegt, letzter_eingriff_tag, foto_front_tag, foto_zugang_tag, uhrzeit_gleichentag) are already documented in the schema. The description mentions the concept of a last change only in passing and adds no meaning about how those inputs combine. Baseline 3 applies when the schema carries the parameter burden.

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 states an outcome ('separate usable current pictures from pre-change images') and a constraint ('limit existing photos to the state after the last mentioned change'), so the general intent is graspable. However, the verb is abstract ('begrenzen'/'separate') and it never says what the tool actually produces — a filtered set, a verdict, or a flag. It does not distinguish itself from the many similarly abstract sibling decision tools.

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?

There is no statement of when this tool should be chosen, what precondition triggers it, or which sibling to use instead (e.g. the photo-excerpt or sample-vs-single-photo tools). The agent must infer the use case entirely from the phrase 'pre-change images'.

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