Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Book Owner-Paid Expense

create_owner_expense_reimbursement

Create a journal entry to reimburse an owner for business expenses paid personally, with support for VAT rates and deduction modes.

Instructions

Create a journal for a business expense paid personally by the owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vat_rateYesVAT rate as decimal (e.g. 0.24 for 24%; 0 = no VAT/non-deductible). Must be a fraction, NOT a percentage — use 0.24, not 24.
net_amountYesNet amount (without VAT)
vat_amountNoExact VAT amount (overrides vat_rate if provided)
descriptionYesExpense description
vat_accountNoInput VAT account (default 1510)
effective_dateYesExpense date (YYYY-MM-DD)
document_numberNoReceipt/document number
expense_accountYesExpense account number (e.g. 5000, 6000)
owner_client_idYesOwner/shareholder client ID
payable_accountNoPayable to owner account (default 2110)
vat_deduction_modeNoVAT deduction mode. Use partial with deductible_vat_amount.
deductible_vat_amountNoDeductible part of VAT when vat_deduction_mode=partial, or an explicit deductible VAT amount to override the default or configured ratio.
Behavior2/5

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

Annotations provide no hints (all false), but the description does not compensate. It omits behavioral traits like idempotency, side effects, or required permissions. Simply stating 'Create a journal' is insufficient for a complex write operation.

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?

Very concise single sentence. It is front-loaded with the key purpose. However, given the tool's complexity (12 parameters), slightly more detail would not harm conciseness.

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 12 parameters and no output schema, the description is too minimal. It does not explain what the resulting journal looks like, which accounts are affected, or the typical workflow context.

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 baseline is 3. The description adds no parameter-level information beyond what the 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?

Description clearly states the specific action ('Create a journal') and resource ('business expense paid personally by the owner'). It distinguishes from generic journal creation tools like create_journal.

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 explicit guidance on when to use this tool versus alternatives such as create_journal or other expense-related tools. The description lacks context for selection.

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