Dollea Beauty Coworking

Eigene Rechnung abrufen

coworking_get_invoice

Read-onlyIdempotent

Eine eigene Rechnung anhand ihrer Kennung abrufen. Eine fremde oder unbekannte Kennung wird als nicht verfügbar behandelt.

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": {
      "invoice_id": "<invoice_id>"
    },
    "name": "coworking_get_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de
`invoice_id`	Yes	Kennung einer eigenen Rechnung aus coworking_list_invoices.

Output Schema

Name	Required	Description	Default
`business`	Yes
`language`	Yes
`timezone`	Yes
`local_date`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover safety properties (read-only, idempotent, non-destructive, closed-world). The description adds meaningful behavioral context beyond annotations: it restricts access to 'eigene' invoices and specifies that foreign or unknown identifiers are treated as unavailable, which is an important authorization/scoping behavior.

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 short sentences with no redundancy. The primary purpose is front-loaded, followed by the edge-case behavior, making it efficient and easy to scan.

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?

Given a full input schema with 100% description coverage, a present output schema, and annotations covering safety, the description provides everything an agent needs to select and invoke the tool correctly: purpose, required identifier, and edge-case behavior for foreign or unknown IDs.

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 schema already documents both parameters fully, including the invoice_id source and language enum. The description only repeats that the invoice is retrieved by its identifier and adds a note about unknown IDs, which is more behavioral than parameter-specific; baseline 3 is appropriate.

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?

The description states a specific verb (abrufen) and resource (eigene Rechnung) with a clear scope: retrieving a single invoice by its identifier. It implicitly distinguishes itself from list-oriented siblings like coworking_list_invoices by emphasizing 'eine eigene Rechnung' and 'anhand ihrer Kennung'.

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?

The description gives a clear context for using the tool when you have an invoice ID, and notes that foreign or unknown IDs are treated as unavailable. However, it does not explicitly name alternatives such as coworking_list_invoices or state when not to use this tool, leaving usage mostly implied.

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

All Dollea Beauty Coworking 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?