Skip to main content
Glama
AIWerk

mcp-server-smallinvoice

by AIWerk

create_invoice

Create a new invoice for Swiss SMEs with customizable fields including contact, dates, currency, positions, and discounts.

Instructions

Creates new invoice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberNounique number - default value: 'next free number'
contact_idYesid of a contact
contact_address_idYesid of a contact's address
contact_prepage_address_idNoid of a contact's prepage address
contact_person_idNoid of a contact's person
dateYesdate of the invoice
dueYesdue date of the invoice
period_fromNoservice period from
period_toNoservice period to
period_textNoservice/delivery
currencyYescurrency (e.g. CHF, EUR)
vat_includedNowhether prices in invoice include VAT - default value: false
discount_rateNooptional discount rate - default value: 0.0
discount_typeNooptional discount type; possible values: A - amount, P - in % - default value: 'P'
cash_discount_rateNocash discount value in %
cash_discount_dateNocash discount deadline date
bank_account_idNobank account id
isr_idNoISR id
isr_positionNoISR position; possible values: A - additional page, F - first page, L - last page - default value: 'A'
payment_link_paypalNowhether to print PayPal link on invoice - default value: false
payment_link_postfinanceNowhether to print PostFinance link on invoice - default value: false
payment_link_payrexxNowhether to print Payrexx link on invoice - default value: false
payment_link_smartcommerceNowhether to print SmartCommerce link on invoice - default value: false
languageYeslanguage; possible values: de, en, es, fr, it
signature_idNosignature id
layout_idNolayout id
notesNooptional notes
custom_fieldsNocustom fields values
positionsYespositions objects
textsNotexts objects
free_textsNofree texts objects
workflowNoworkflow objects
Behavior2/5

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

The description provides no behavioral information beyond what annotations already indicate (non-read-only, non-destructive, open world). It doesn't disclose if the invoice is created as a draft, whether it triggers email sending, or what the return value is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence) but at the cost of meaningful content. It is structurally minimal but lacks substance to earn a higher score.

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

Completeness2/5

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

Given the tool's complexity (32 parameters, 7 required, no output schema), the description is woefully incomplete. It does not explain what an invoice represents, how the parameters relate to real-world invoice creation, or what happens after creation.

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?

The input schema covers all 32 parameters with individual descriptions (100% coverage), so the description adds no additional meaning. Baseline score of 3 is appropriate as schema already does the heavy lifting.

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

Purpose3/5

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

The description 'Creates new invoice' clearly states the verb and resource, matching the tool name. However, it fails to distinguish this from many other create_* sibling tools (e.g., create_offer, create_delivery_note) by providing any unique context about invoices.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool vs. alternatives like update_invoice or list_invoices. There is no mention of prerequisites (e.g., existing contacts) or typical workflow context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIWerk/mcp-server-smallinvoice'

If you have feedback or need assistance with the MCP directory API, please join our Discord server