Bokadirekt MCP Server and API by Cotlet

Move booking in Bokadirekt

bokadirekt_move_booking

Read-onlyIdempotent

Move booking in the user's own Bokadirekt account from ChatGPT, Claude or any AI agent. Returns how to do it in Bokadirekt step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bokadirekt Cloud Browser. Bokadirekt's official API: Yes, but it only reads.

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": "bokadirekt_move_booking"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself,' which is exactly the non-obvious behavior an agent needs. It also discloses the return content (screens, buttons, fields) and the follow-up tool family. It stops short of stating login/session prerequisites for the Cloud Browser.

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 key facts are front-loaded: what it does, that it returns instructions rather than acting, and which tools execute the action. The 'from ChatGPT, Claude or any AI agent' clause is mild filler but does not obscure the message.

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 this covers the essentials: behavior (read-only instructions), return shape (step-by-step screens/buttons/fields), and the handoff to browser tools. Only session/auth preconditions for the Bokadirekt Cloud Browser are left implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a parameterless tool is 4, and nothing in the description creates confusion about inputs.

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

Purpose4/5

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

States a specific verb and resource (move a booking in the user's own Bokadirekt account) and immediately clarifies that the tool does not actually perform the move but returns step-by-step UI instructions. The name suggests a mutation while the real behavior is guidance, but the description resolves that ambiguity rather than hiding it.

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?

Gives clear usage context: call this to learn how to move a booking, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. It also notes the official API only reads, explaining why a browser path is required. It does not explicitly contrast with bokadirekt_cancel_booking or bokadirekt_create_booking as alternatives.

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

All Bokadirekt 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?