Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Create Sale Invoice

create_sale_invoice

Create a sales invoice with itemized products, payment terms, and accounting accounts. Supports credit invoices and auto-assigned invoice numbers.

Instructions

Create a sales invoice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesInvoice items [{products_id, custom_title, amount, unit_net_price, sale_accounts_id?, sale_accounts_dimensions_id?, vat_accounts_id?, cl_sale_articles_id?, discount_percent?, projects_project_id?, projects_location_id?, projects_person_id?}]. sale_accounts_dimensions_id is REQUIRED when the revenue account has dimensions. Note: SaleInvoicesItems schema has no vat_accounts_dimensions_id field — only the purchase side does.
notesNoInternal notes
term_daysYesPayment term in days
clients_idYesBuyer client ID
create_dateYesInvoice date (YYYY-MM-DD)
journal_dateYesTurnover date (YYYY-MM-DD)
number_suffixNoInvoice number suffix (omit or empty string for auto-assign from invoice series)
cl_countries_idNoCountry (default EST)
cl_templates_idYesInvoice template ID
cl_currencies_idNoCurrency (default EUR)
sale_invoice_typeNoType: INVOICE or CREDIT_INVOICE
show_client_balanceNoShow client balance on invoice
Behavior2/5

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

Annotations already indicate this is a non-readonly, non-destructive creation action. The description adds no further behavioral details, such as whether the invoice is created as draft or confirmed, or any side effects.

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 very concise with one short sentence, which is front-loaded but underspecified for a tool with 12 parameters. It earns its place but is too brief.

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

Completeness1/5

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

Given the complexity (12 parameters, 6 required, no output schema), the description is extremely incomplete. It fails to mention return value, prerequisites, or potential errors, making it inadequate for effective tool selection.

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 baseline is 3. The description does not add extra meaning beyond what the parameter descriptions already provide.

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 clearly states 'Create a sales invoice', specifying the verb and resource. It distinguishes from sibling tools like create_purchase_invoice and confirm_sale_invoice.

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 provided on when to use this tool versus alternatives such as create_recurring_sale_invoices or confirm_sale_invoice. The description lacks any context about appropriate usage 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/iseppo/e-arveldaja-mcp'

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