Skip to main content
Glama
Frihet-io

Frihet MCP Server

Apply Late Fee

apply_late_fee

Apply late payment interest to overdue invoices. Automatically calculate fees based on EU directive or custom parameters, and generate a linked debit note.

Instructions

Apply late payment interest to an overdue invoice. Calculates interest based on EU Late Payment Directive (8% default) or auto-calculates from days overdue. Creates a debit note linked to the original invoice. / Aplica intereses de demora a una factura vencida. Calcula intereses segun la Directiva Europea de Morosidad (8% por defecto) o los calcula automaticamente a partir de los dias de retraso. Crea una nota de debito vinculada a la factura original.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoiceIdYesID of the overdue invoice / ID de la factura vencida
amountNoOverride fee amount. If omitted, auto-calculated from days overdue and legal rate. / Importe de la comision. Si se omite, se calcula automaticamente.
daysOverdueNoOverride days overdue count. If omitted, calculated from due date. / Dias de retraso. Si se omite, se calcula a partir de la fecha de vencimiento.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
idYes
messageNo
Behavior4/5

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

Annotations (readOnlyHint=false) indicate mutation, and the description adds context: it creates a debit note and auto-calculates interest. It explains side effects beyond annotations, though reversibility or permissions are not mentioned.

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?

The description is concise with front-loaded purpose, though bilingual adds slight redundancy. Each sentence provides value, and the structure is clear.

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?

Given the presence of an output schema (not shown but indicated), the description covers necessary behavioral context (debit note creation, auto-calc). With 3 parameters fully described and annotations provided, it is sufficiently complete.

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% with detailed descriptions for all 3 parameters. The description repeats the auto-calc behavior but does not add significant new meaning beyond the schema, so baseline 3 is appropriate.

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 the tool applies late payment interest to an overdue invoice, specifying the resource (invoice) and actions (apply fee, create debit note). It distinguishes from sibling tools like mark_invoice_paid by focusing on late fee calculation and debit note creation.

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 overdue invoices, mentioning auto-calculation from days overdue and legal rate. It provides context (EU directive, debit note) but does not explicitly state when not to use or compare with alternatives, though the purpose is clear.

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/Frihet-io/frihet-mcp'

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