Skip to main content
Glama
berthelius

Frihet MCP Server

Approve Leave Request

leave_approve
Idempotent

Approve a pending leave request by providing its ID. Logs the decision with timestamp and approver; idempotent design prevents duplicate approvals.

Instructions

TRUST AREA — HR DECISION. Approve a pending leave request. Logs decision with timestamp and approver. Idempotent: re-approving an already approved leave is a no-op. / AREA DE CONFIANZA — DECISION RRHH. Aprueba una solicitud de permiso pendiente. Registra la decision.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoOptional approval note / Nota de aprobacion opcional
leaveIdYesLeave request ID / ID de la solicitud

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
typeNoLeave type slug (vacation, sick, personal, etc.)
reasonNo
statusNo
endDateNo
createdAtNo
decidedAtNo
decidedByNo
startDateNo
updatedAtNo
employeeIdNo
durationDaysNo
decisionReasonNo
Behavior5/5

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

Description adds context beyond annotations: logs decision with timestamp and approver, states idempotency (aligns with idempotentHint). No contradiction with annotations.

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 sentences front-load key info and include Spanish translation without extra fluff. Every sentence is relevant.

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, description covers purpose, side effects, preconditions (pending), and idempotency. Complete for a simple approval tool.

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 bilingual descriptions, so description adds no extra parameter meaning; 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 uses specific verb 'Approve' and resource 'pending leave request', clearly distinguishing from sibling tools like leave_reject and leave_cancel.

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?

While no explicit when-not/alternatives are stated, the name and description implicitly guide an AI agent to use this for approving pending leaves, and the sibling set provides clear contrasts.

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