Skip to main content
Glama
berthelius

Frihet MCP Server

Refund POS Sale

refund_sale
DestructiveIdempotent

Process full or partial refunds for POS sales. Refunds are irreversible and returned to original payment method. Requires confirm=true to proceed.

Instructions

Refund a POS sale in full or partially. This action is irreversible — the customer will receive a refund to their original payment method. You MUST pass confirm=true to proceed. Optionally specify amountCents for a partial refund (defaults to full refund). / Reembolsa una venta POS total o parcialmente. Accion irreversible. Debes pasar confirm=true. Pasa amountCents para reembolso parcial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSale ID to refund / ID de venta a reembolsar
reasonNoRefund reason / Motivo del reembolso
confirmYesMust be true to proceed. Safety gate for destructive action. / Debe ser true para continuar. Confirmacion obligatoria.
amountCentsNoPartial refund amount in cents. Omit for full refund. / Importe parcial en centimos. Omitir para reembolso completo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
reasonNo
saleIdYes
statusYes
currencyYes
createdAtYes
amountCentsYes
Behavior5/5

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

Description adds 'This action is irreversible' and 'safety gate for destructive action' beyond annotations which already indicate destructiveHint=true. No contradiction.

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 concise sentences in English and Spanish covering all key points with no redundancy. Front-loaded with essential information.

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

Completeness5/5

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

Given output schema exists, the description adequately covers irreversibility, required confirm, and partial refund option. Complete for a destructive action tool.

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%, but description adds useful defaults (full refund) and clarifies confirm=true requirement, adding value beyond 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 'Refund a POS sale in full or partially' with specific verb and resource. It distinguishes from sibling 'refund_deposit' by specifying POS sale.

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?

Explicitly states requirement to pass confirm=true and optional amountCents for partial refund. Provides clear usage context but does not list when not to use or alternatives.

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