nkfix-mcp

Overview Schema Source Related Servers Discussions Admin

Abrechnung im Detail

get_statement

Read-only

Fetches a billing statement by ID to show itemized costs, tenant share, prepayments, balance, prepayment adjustment, and due dates.

Instructions

Ergebnis einer Abrechnung: Kosten je Position mit Anteil des Mieters, Vorauszahlungen, Saldo, Anpassung der Vorauszahlung und Fristen.

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": {
      "statement_id": "<statement_id>"
    },
    "name": "get_statement"
  }
}

Input Schema

Name	Required	Description	Default
`statement_id`	Yes	ID der Abrechnung, siehe Werkzeug list_statements

Output Schema

Name	Required	Description
`id`	Yes
`tenant`	Yes
`balance`	Yes	positiv: Nachzahlung des Mieters, negativ: Guthaben
`version`	Yes
`end_date`	Yes
`outdated`	Yes
`property`	Yes
`warnings`	Yes
`apartment`	Yes
`tenant_id`	Yes
`line_items`	Yes
`start_date`	Yes
`total_costs`	Yes
`delivered_at`	Yes
`payment_status`	Yes
`advance_payments`	Yes
`objection_deadline`	Yes
`outstanding_amount`	Yes
`statement_deadline`	Yes
`new_advance_payment`	Yes	vorgeschlagene neue monatliche Vorauszahlung, oder nur ein reason, warum es keinen Vorschlag gibt

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

C2.6/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. Beyond that the description only enumerates returned data categories, which duplicates the output schema, and says nothing about behavior on an unknown statement_id, permissions, or whether the statement is computed on demand.

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?

It is a single short sentence-fragment, so it is compact, but it is a comma-separated field list rather than a front-loaded statement of purpose. The opening 'Ergebnis einer Abrechnung' spends the most prominent position on a vague framing instead of the action.

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?

The tool is simple (one ID parameter, read-only, output schema present), so the description need not explain return values. However, it spends its whole length on return contents that the output schema already defines, leaving the actual usage context unaddressed.

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?

There is a single required parameter at 100% schema description coverage, so the schema already explains statement_id and even cross-references list_statements. The description adds no meaning about the identifier format or lookup semantics, so the baseline of 3 applies.

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 characterizes the payload ('Ergebnis einer Abrechnung') rather than stating the action; the retrieval verb is only implied by the name get_statement. It does not distinguish itself from list_statements or precheck_statement, so an agent must infer the detail-vs-list relationship on its own.

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 to call this tool, no prerequisites (e.g., a statement must already exist or be computed), and no mention of alternatives such as list_statements for browsing. Only the schema's parameter note points to a sibling, which is schema text rather than description guidance.

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