Skip to main content
Glama

getecoback-climate-weather

philips_na352_programmende_signal_ausgabe_unbekannt

Read-only

Ein einzelnes fotografiertes Ende ohne Zuordnung zum kleinen oder großen Korb im Protokoll offen lassen — Resolve ambiguous end evidence instead of inferring the other basket’s state.

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": {
      "modell_und_sitzung_belegt": "<modell_und_sitzung_belegt>",
      "eindeutige_endanzeige": "<eindeutige_endanzeige>",
      "meldung_anzeige_unterstuetzt": "<meldung_anzeige_unterstuetzt>",
      "sync_markierung_gesehen": "<sync_markierung_gesehen>"
    },
    "name": "philips_na352_programmende_signal_ausgabe_unbekannt"
  }
}

Input Schema

NameRequiredDescriptionDefault
eindeutige_endanzeigeYesWelchem Korb ist das neueste bestätigte Ende anhand der Aufzeichnung zugeordnet?
sync_markierung_gesehenYesWurde die Synchronisierungsmarkierung unabhängig davon im selben Lauf gesehen?
modell_und_sitzung_belegtYesGehören Anzeige oder Notiz eindeutig zu einer Sitzung am deutschen NA352/00?
meldung_anzeige_unterstuetztYesIst die betrachtete Meldung tatsächlich als Programmende dieser Anzeige identifiziert?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuine behavioral trait: the tool preserves ambiguity instead of guessing, which tells the agent the outcome is an 'open' classification rather than a resolved basket. However, the phrase 'im Protokoll offen lassen' gestures at writing a log entry, which sits awkwardly beside readOnlyHint and is not clarified, and nothing is said about what is returned.

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?

Two compact clauses with the operative action front-loaded before the em-dash rationale; nothing is padded. The only slack is the bilingual duplication of the same idea in German and English.

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 four-parameter, fully-required decision tool with no output schema, the description conveys the decision stance (leave open, do not infer) but not the result shape or how the four evidence checks combine into an outcome. The rich schema descriptions compensate partially, leaving a moderate gap.

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 each of the four required parameters carries a German description plus an explicit enum (gross/klein/beide/offen), so the schema carries the semantic load. The description adds no meaning beyond it, which is the expected baseline here.

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 concrete action and object: leave a single photographed end without small/large basket assignment open in the protocol, rather than inferring the other basket's state. The action (record/keep ambiguous evidence as unassigned) is specific, though the opaque machine-generated tool name adds no help and no sibling is named for contrast.

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?

It implies the triggering condition (ambiguous end evidence) and states a negative rule — do not infer the other basket's state — which functions as a when-not hint. It gives no explicit routing against near neighbors such as the sync/end-observation tools, so an agent must infer when this applies versus those.

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