nkfix-mcp

Overview Schema Source Related Servers Discussions Admin

Fristen

list_deadlines

Read-only

Retrieves upcoming billing, objection, calibration, meter-reading, advance-payment, and rent-increase deadlines, optionally limited to a date, with statement IDs and billing periods where relevant.

Instructions

Anstehende Termine und Fristen: Abrechnungs-, Einwendungs- und Eichfristen, Ablesungen, neue Vorauszahlungen und die früheste Mieterhöhung. Abrechnungs- und Einwendungsfristen nennen die Abrechnung (statement_id) und ihren Abrechnungszeitraum.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_deadlines"
  }
}

Input Schema

Name	Required	Description	Default
`until`	No	nur Termine bis zu diesem Datum (YYYY-MM-DD)

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`items`	Yes
`omitted`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world read operation. The description adds useful behavioral detail by explaining that Abrechnungs- und Einwendungsfristen name the related statement_id and its billing period. It does not describe ordering, time window semantics, or pagination, so it adds some but not rich behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences, front-loads the resource scope by listing deadline categories, and then adds the statement_id linkage. Every phrase contributes to understanding what deadlines are returned, with no unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only listing tool with an output schema, the description is nearly complete: it names the deadline categories and explains the statement relationship. The main minor gap is that it does not define how 'upcoming' is measured or how results are ordered, though the optional until parameter is schema-documented.

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 the single optional 'until' parameter is already fully documented in the input schema. The description does not mention the parameter or add formatting or filtering semantics beyond what the schema provides, which matches the baseline of 3 for high schema coverage.

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 identifies a specific resource, 'Anstehende Termine und Fristen,' and enumerates the deadline categories covered, including Abrechnungs-, Einwendungs- und Eichfristen, Ablesungen, Vorauszahlungen, and Mieterhöhung. It is clear what the tool returns, though it does not explicitly differentiate itself from the many sibling list_* tools by naming alternatives.

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?

Usage is implied by 'Anstehende Termine und Fristen' and by the enumerated deadline types, so an agent can infer this is the tool for upcoming deadline queries. However, there is no explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named for related listing tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.