Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Book Owner-Paid Expense

create_owner_expense_reimbursement

Record a journal entry for a business expense paid personally by the owner, specifying net amount, VAT rate, and expense account.

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.
Behavior3/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds no additional behavioral details beyond stating it creates a journal.

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?

Single sentence, front-loaded with clear action and context. No unnecessary words.

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

Completeness3/5

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

For a creation tool with 12 parameters and no output schema, the description is minimal. It does not mention return values or additional context like default accounts, which would be helpful.

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 adds no extra meaning to parameters beyond what's already in the schema.

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 it creates a journal for a specific type of expense (owner-paid). It distinguishes itself from sibling tools like 'create_journal' and 'create_purchase_invoice' by specifying the exact context.

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

Usage Guidelines4/5

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

The description implies usage for owner reimbursements, but does not explicitly state when not to use it or compare with alternatives. However, the name and context provide sufficient guidance.

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