Skip to main content
Glama
Valtterios

kitsas-mcp

by Valtterios

add_purchase_invoice

Create a purchase invoice draft for review and approval. Debits expense lines, credits the default bank or specified account, and does not book until approved.

Instructions

Create a purchase invoice as a DRAFT. It does not enter the ledger and gets no voucher number until a human reviews and approves it in Kitsas; this tool can never book money on its own. Expense lines are debited; the total is credited to the bank account unless credit_account says otherwise. Call suggest_account first so the supplier keeps landing on the same account it always has.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ibanNo
linesYesExpense lines: account (int), amount (euros as a string), description (optional)
due_dateNoYYYY-MM-DD
pdf_pathNoThe original invoice, attached to the voucher
referenceNo
business_idNo
descriptionNo
booking_dateYesYYYY-MM-DD, must be in an open fiscal year
invoice_dateNoYYYY-MM-DD
supplier_nameYes
credit_accountNoDefaults to the bank account

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations were provided, but the description thoroughly discloses behavior: it never books money, remains a draft, lacks a voucher number until approval, and details debit/credit entry logic, including the credit_account override.

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?

The description is compact, three sentences, with no fluff. It front-loads the key draft behavior and then explains accounting details and a prerequisite, all relevant and efficiently stated.

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?

Though there is no output schema, the description explains the tool's side effects and accounting flow well. Minor gaps remain regarding expected return values or error conditions, but these are not critical given the overall clarity.

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 description adds meaning for credit_account and booking_date (open fiscal year), but many parameters (iban, reference, business_id, description, invoice_date, supplier_name) are only defined by schema names or minimal schema descriptions. Schema coverage is only 55%, leaving gaps that the description does not fill.

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?

Clearly states the action 'Create a purchase invoice as a DRAFT' with a specific resource. The draft status and lack of ledger impact differentiate it from other tools.

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

Usage Guidelines5/5

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

Provides explicit guidance to call suggest_account first for consistent supplier accounts, and explains the draft workflow and accounting treatment, helping the agent choose when to use this tool.

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

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/Valtterios/kitsas-mcp'

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