Dollea Beauty Coworking

Eigene Rechnungen lesen

coworking_list_invoices

Read-onlyIdempotent

Rechnungen des aktuell verbundenen Kontos mit Beträgen, Fälligkeit und geschütztem Download lesen. Keine Verwaltungsnotizen oder fremden Rechnungen ausgeben.

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": "coworking_list_invoices"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximale Anzahl zurückgegebener Ergebnisse innerhalb der veröffentlichten Grenze.
`offset`	No	Ergebnisposition für die nächste Seite; next_offset aus der vorherigen Antwort verwenden.
`language`	No	Gewünschte Sprache für Texte und Anzeigeformate: de, en oder ru.	de

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower; the description adds value beyond that by disclosing the return content (amounts, due dates) and a protected download affordance, plus an explicit output-exclusion rule. It still does not mention pagination behavior, which limit/offset imply.

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?

Two tightly written sentences with the positive scope front-loaded followed by the exclusion boundary; no filler. Slightly dense but every clause carries information.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. With all three parameters optional and schema-documented, the description covers scope and exclusions adequately; only an explicit alternative-tool pointer is missing.

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 limit, offset and language fully. The description adds no syntax, format or constraint detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Rechnungen ... lesen') scoped to the currently connected account, and enumerates what is returned (Beträge, Fälligkeit, geschützter Download). It implies a bulk list operation distinct from the singular coworking_get_invoice, though it never names that sibling explicitly.

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?

Provides a scope boundary ('Keine Verwaltungsnotizen oder fremden Rechnungen ausgeben') that implies when this tool applies, but gives no explicit when-to-use condition or routing to alternatives such as coworking_get_invoice for a single record.

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?