Skip to main content
Glama

Rechnungen ohne Konto übernehmen

import_invoices
Idempotent

Store the invoices this chat created without an account (the PDFs from finalize_invoice) in the connected facturo account. They keep the user's own invoice numbers and facturo's numbering continues after the highest one. Only call it after the user said yes to the offer, ideally before the first invoice is created in the account so the sequence stays in order. An invoice already in the account is never stored twice.

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

Input Schema

NameRequiredDescriptionDefault
invoice_numbersNoOnly these numbers (from importable_invoices); default: all of them

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false; the description goes further by explaining the numbering behavior (user's own numbers preserved, facturo's sequence continues after the highest) and the consent gate. It still omits what happens on partial failure or what the call returns, but that is beyond the annotation baseline.

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?

Four front-loaded sentences cover source, numbering, consent and timing, and the 'never stored twice' reassurance closes it. No filler and no repetition of the title.

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 consent-gated mutation with one optional parameter and full annotation coverage, the description supplies the ordering, numbering and dedup semantics an agent needs. The missing piece is failure/return behavior, which the absence of an output schema leaves unexplained.

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 coverage is 100%, so the single optional 'invoice_numbers' parameter is already documented in the schema with its source and default. The description adds nothing further about the parameter, so the baseline 3 applies.

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 ('Store the invoices ... in the connected facturo account') and pins the exact source of the artifacts ('the PDFs from finalize_invoice'), which cleanly separates it from finalize_invoice and preview_invoice.

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 a hard precondition ('Only call it after the user said yes to the offer') plus a timing preference ('ideally before the first invoice is created in the account so the sequence stays in order'). Clear context, but no explicit when-not guidance or named alternative for the case where the ordering window has already been missed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources