Civitatis MCP Server and API by Cotlet

Get booking details in Civitatis

civitatis_get_booking_details

Read-onlyIdempotent

Get booking details in the user's own Civitatis account from ChatGPT, Claude or any AI agent. Returns how to do it in Civitatis step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Civitatis Cloud Browser. Civitatis's official API: Civitatis has no public API for suppliers (checked 11 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": "civitatis_get_booking_details"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description adds crucial behavioral context not covered by annotations, specifically stating that it 'opens nothing by itself' and outlines the underlying limitation that there is 'no public API for suppliers.' This defines the tool's informational, non-destructive nature beyond the hints provided.

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?

While the information is relevant, the description is verbose for a tool with zero parameters. Phrases like 'from ChatGPT, Claude or any AI agent' are redundant conversational fluff that lowers the score.

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 that this tool's primary function is to provide a user manual for a UI interaction, the description is perfectly complete. It covers the 'what,' the 'how,' and the necessary 'next steps' involving sibling tools, making the workflow entirely clear.

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?

Since the tool has zero parameters, the description must carry all context. It provides the necessary high-level semantic understanding of the tool's function even though the schema is empty. A score of 4 acknowledges this full burden of contextual clarity.

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 clearly identifies the goal (getting booking details) but focuses more on the procedural guidance (AI context, UI steps) rather than the resource interaction itself. It defines what the tool delivers—instructions—but is less specific about the data transformation or retrieval mechanism beyond implying UI manipulation.

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

Usage Guidelines5/5

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

This tool excels at usage guidance by immediately establishing its non-executable role. It clearly dictates the necessary next step: the user must follow the instructions and execute the actions using the `cotlet_browser_*` sibling tools.

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

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