Bokadirekt MCP Server and API by Cotlet

Send booking message in Bokadirekt

bokadirekt_send_booking_message

Read-onlyIdempotent

Send booking message 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_send_booking_message"
  }
}

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 already declare readOnlyHint=true and idempotentHint=true, and the description corroborates them with 'opens nothing by itself' rather than contradicting. It adds genuine context the annotations cannot carry: the return value is a step-by-step UI walkthrough (screens, buttons, fields) and that the official API is read-only, which is why a browser is required.

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?

Three short sentences, front-loaded with the action and immediately qualifying it with 'opens nothing by itself.' Slightly dense parenthetical and the dangling 'Bokadirekt's official API: Yes, but it only reads' clause are minor inefficiencies but the routing information lands clearly.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description supplies exactly what is missing: what it returns and which tools finish the job. It could mention the prerequisite of an open/logged-in Cloud Browser session, which is the only notable gap.

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 no parameter meaning for the description to supplement; baseline 4 applies. The description correctly implies the only implicit input is the user's own Bokadirekt account context.

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?

The description states a concrete resource (booking message) and, crucially, corrects the misleading verb by saying it 'opens nothing by itself' and instead 'Returns how to do it in Bokadirekt step by step.' An agent knows this is a guidance/instruction tool, not a sender, and is pointed at the cotlet_browser_* siblings for the actual action.

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?

It gives explicit sequencing: call this first to get the screens/buttons/fields, then perform the action with the cotlet_browser_* tools in the user's Cloud Browser, and explains the constraint that the official API 'only reads.' No explicit exclusions are stated, so it stops just short of a 5.

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?