Skip to main content
Glama
berthelius

Frihet MCP Server

Create Quote

create_quote

Generate a client quote with line items and optional details. Quotes default to draft status and can be converted to invoices later.

Instructions

Create a new quote/estimate for a client. Requires client name and at least one line item. Quotes can later be converted to invoices. Defaults to draft status. Example: clientName='Acme Corp', items=[{description:'Design', quantity:1, unitPrice:3000}], validUntil='2026-04-30' / Crea un nuevo presupuesto. Requiere nombre del cliente y al menos un concepto. Los presupuestos se pueden convertir en facturas despues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesLine items (each with description, quantity, unitPrice) / Conceptos del presupuesto
notesNoAdditional notes shown on the quote / Notas adicionales
statusNoQuote status (default: draft) / Estado del presupuesto
dueDateNoDue date in ISO 8601 (YYYY-MM-DD) / Fecha de vencimiento
taxRateNoTax rate % (e.g. 21 IVA, 7 IGIC) / Porcentaje de impuesto
clientIdNoExisting client ID — server back-fills taxId/address / ID de cliente existente
irpfRateNoIRPF withholding % (retencion autonomo ES) / Retencion IRPF %
issueDateNoIssue date in ISO 8601 (YYYY-MM-DD), defaults to today / Fecha de emision
clientNameYesClient name / Nombre del cliente
validUntilNoExpiry date in ISO 8601 (YYYY-MM-DD) / Fecha de validez
clientTaxIdNoClient tax ID (NIF/CIF/VAT) / NIF/CIF del cliente
clientAddressNoClient billing address / Direccion fiscal del cliente
clientLocationNoFiscal zone driving IVA vs IGIC vs exempt / Zona fiscal
equivalenceSurchargeRateNoRecargo de equivalencia % / Recargo de equivalencia %

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
itemsNo
notesNo
totalNo
statusNo
createdAtNo
updatedAtNo
clientNameNo
validUntilNo
Behavior3/5

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

Annotations provide no hints (all false), so the description must carry the burden. It discloses requirements (client name, line items), default status (draft), and conversion ability, but does not mention side effects, authorization, or idempotency. Adequate but not comprehensive.

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?

Two focused sentences plus an example. Bilingual content is concise and adds no fluff. Every sentence earns its place.

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 14 parameters and output schema exists, the description covers essentials: purpose, requirements, default status, and conversion. Lacks explanation of tax rate interactions, but schema handles that. Mostly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 value with an example (clientName, items, validUntil) and clarifies default status (draft), which is not specified in the schema. Thus, above baseline.

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 new quote/estimate for a client,' specifying the verb and resource. It distinguishes from siblings like create_invoice by noting quotes can be converted to invoices later.

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

Usage Guidelines3/5

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

The description mentions quotes can be converted to invoices, which implies an alternative, but does not explicitly state when to use this tool versus other create_* tools. Lacks clear when-not or comparative 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/berthelius/frihet-mcp'

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