Personio MCP Server and API by Cotlet

Approve time off in Personio

personio_approve_time_off

Read-onlyIdempotent

Approve time off in the user's own Personio account from ChatGPT, Claude or any AI agent. Returns how to do it in Personio step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Personio Cloud Browser. Personio's official API: Personio has a public REST API and an official MCP server in closed beta (checked 16 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "personio_approve_time_off"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds the important context that it opens nothing by itself and only returns instructions, plus points to browser tools for the actual action. It still omits prerequisites such as needing a Personio session or an open browser.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core behavior is stated, but the second half includes an API/MCP status note ('checked 16 Oct 2026') that does not help selection or invocation and dilutes the message. The key clarification that it opens nothing is buried after an action-sounding opener.

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?

For a zero-parameter, no-output-schema guide tool, the description explains the return content (step-by-step screens, buttons, fields) and that execution happens via browser tools. Missing prerequisites are a minor gap, but the definition is otherwise complete enough to call correctly.

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?

There are zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description does not need to add parameter meaning beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states that it returns step-by-step instructions (screens, buttons, fields) rather than performing approval, but the name/title 'Approve time off' and opening sentence imply an action tool. It points to cotlet_browser_* for execution but does not clearly differentiate from sibling Personio tools such as personio_request_time_off.

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

Usage Guidelines2/5

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

It describes a workflow ('then do it with the cotlet_browser_* tools') but gives no explicit when-to-use or when-not-to-use guidance versus Personio's API/MCP or other Personio tools. The API/MCP status sentence is context, not decision criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Personio MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?