Skip to main content
Glama

getecoback-climate-weather

beleg_datum_redaktionsstand_trennen

Read-only

Testzeitpunkt, Abruf und Seitenaktualisierung im Nachweis auseinanderhalten — Separate the actual test date from article and retrieval dates.

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": {
      "test_strukturiert": "<test_strukturiert>",
      "aktualisierung": "<aktualisierung>",
      "abruf_notiert": "<abruf_notiert>"
    },
    "name": "beleg_datum_redaktionsstand_trennen"
  }
}

Input Schema

NameRequiredDescriptionDefault
abruf_notiertYesEigenes Abrufdatum nachvollziehbar notiert?
aktualisierungYesAuf der Zusammenfassung ist nur ein eigenes Aktualisierungsdatum genannt?
test_strukturiertYesTestzeitpunkt steht im Primärbericht?

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, so the safety profile is covered. The description adds that three distinct date concepts are being disentangled, but it never says what the tool concludes or returns from the three booleans — whether it flags an inconsistency, normalizes a citation, or emits a verdict. That behavioral gap matters for a decision-style tool.

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 a German statement and an English gloss, front-loaded with the core distinction. Slightly redundant to restate in both languages, but nothing is wasted.

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 three-boolean, no-output-schema tool, the description covers the concepts being compared and annotations cover safety. What is missing is any account of the outcome the caller should expect, which leaves the agent guessing about the tool's actual effect.

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 coverage is 100%, so each boolean is already documented in the schema. The description reinforces the mapping by naming test date, editorial/update date, and retrieval date, which helps the agent read the params, but it adds no threshold logic or guidance on setting the booleans.

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 — separating the actual test date (Testzeitpunkt) from the article's editorial date (Seitenaktualisierung) and the retrieval date (Abruf) within a proof/record. The verb+resource pairing is clear and matches the three boolean parameters. It does not, however, distinguish this tool from the many similarly named 'beleg'-style separation tools in the sibling list.

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 explicit statement of when to invoke this versus other evidence-checking tools, no preconditions, and no exclusions. The context of 'im Nachweis' implies it belongs to a documentation-verification workflow, but the agent must infer that.

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