Skip to main content
Glama
AIWerk

mcp-server-smallinvoice

by AIWerk

update_delivery_note

Update an existing delivery note by providing its ID and modifying fields such as dates, currency, positions, or notes.

Instructions

Updates specified delivery note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delivery_note_idYesdelivery note ID
numberNounique number
contact_idNoid of a contact
contact_address_idNoid of a contact's address
contact_prepage_address_idNoid of a contact's prepage address
contact_person_idNoid of a contact's person
dateNodate of the delivery note
period_textNoservice/delivery
currencyNocurrency (e.g. CHF, EUR)
vat_includedNowhether prices in delivery note include VAT
discount_rateNooptional discount rate
discount_typeNooptional discount type; possible values: A - amount, P - in %
languageNolanguage; possible values: de, en, es, fr, it
signature_idNosignature id
layout_idNolayout id
notesNooptional notes
custom_fieldsNocustom fields values
positionsNopositions objects
textsNotexts objects
free_textsNofree texts objects
Behavior3/5

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

Description matches annotations (readOnlyHint=false, destructiveHint=false). Adds no extra behavioral context beyond annotations, but no contradiction.

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?

Single sentence is concise and front-loaded. Minimal but effective for purpose; could be slightly more informative without being verbose.

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?

With 20 parameters, no output schema, and many siblings, description is too minimal. Does not explain partial update behavior, required fields, or return value.

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 covers 100% of parameters with descriptions. The description adds no additional meaning beyond what schema already provides.

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?

Title 'Update Delivery Note' and description 'Updates specified delivery note' clearly state verb and resource. Distinguishes from siblings like create_delivery_note and delete_delivery_notes.

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 on when to use this tool vs alternatives like create_delivery_note or delete_delivery_notes. Lacks context on prerequisites or typical scenarios.

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