fynsight: MCP server for DATEV

switch_organization

Idempotent

Switch the active organisation for subsequent MCP tool calls (e.g. get_periodic_summaries, query_kpis). The user must be a member and the target org must have an active subscription.

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": {
      "organization_id": "<organization_id>"
    },
    "name": "switch_organization"
  }
}

Input Schema

Name	Required	Description	Default
`organization_id`	Yes	Tenant ID to switch to. Must appear in list_organizations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this as a non-destructive, idempotent, non-read-only mutation. The description adds the key behavioral fact annotations cannot convey: the change is session-scoped and affects all subsequent MCP tool calls. It stops short of saying whether the switch persists across sessions or how failures/errors are surfaced.

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?

Two tight sentences with no filler; the session-wide effect is front-loaded and the preconditions follow. Every clause carries information an agent needs.

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 single-parameter state-switching tool with annotations and no output schema, the description covers effect scope and success preconditions adequately. Only persistence/error behavior is left implicit, which is a modest gap rather than a blocking one.

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% and the parameter is well documented, so the baseline is 3. The description adds real semantic constraints beyond the schema — membership requirement and active-subscription requirement — narrowing which organization_id values are actually valid.

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 ('switch the active organisation') plus the crucial scope effect ('for subsequent MCP tool calls'), with concrete example tools so the agent understands the blast radius. The verb/resource pair cannot be confused with any sibling such as list_organizations.

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

Usage Guidelines4/5

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

Gives clear preconditions for calling it — the user must be a member and the target org must have an active subscription — which effectively tells the agent when the call will succeed. It does not explicitly point to list_organizations for discovery or state what to do on failure, but the schema covers the ID-sourcing requirement, so the gaps are minor.

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?