fynsight: MCP server for DATEV

get-month-run-status

Read-only

Get the status of a Monatsreporting run (month-end close): its phase plus the number of open anomaly cases, open clarification questions and open follow_up checks (follow_ups_open). Pass period (YYYY-MM) to get the active run of that month (not superseded or failed); without a run for it the answer says so. run_id takes precedence over period; with neither, the most recent run is returned. READ ONLY. Starting a run is also possible with start-month-run; approving, publishing and closing happen only in the app.

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": "get-month-run-status"
  }
}

Input Schema

Name	Required	Description	Default
`period`	No	Optional month, YYYY-MM: the active run of that month.
`run_id`	No	Optional UUID of the run. Takes precedence over period.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only and closed-world behavior, and the description reinforces 'READ ONLY' while adding what the agent cannot do here (approve, publish, close). It also discloses the return payload (phase plus three open-item counters) and the edge case that a month without a run is reported rather than erroring. Auth, rate-limit and pagination behavior remain unstated, which is minor for a read-only lookup.

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?

Front-loads the resource and its returned fields, then the parameter selection rules, then the scope boundary. It is dense and one clause runs long, but nearly every sentence carries distinct information.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the returned fields and the empty-result behavior. For a two-optional-parameter read-only status tool, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: period targets the active run specifically (not superseded or failed), and the no-argument case falls back to the most recent run. Only the exact format nuances (UUID vs period validation errors) are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (get the status of a Monatsreporting run) and enumerates exactly what 'status' contains: phase, open anomaly cases, open clarification questions and follow_ups_open. It also separates itself from the sibling start-month-run by declaring that starting, approving, publishing and closing are out of scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit selection rules: use period to fetch the active run of a month, run_id wins when both are present, and with neither the most recent run is returned. It additionally points to start-month-run as the alternative for creating a run and says the other lifecycle steps happen in the app.

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

All fynsight: MCP server for DATEV tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?