Skedda MCP Server and API by Cotlet

List bookings in Skedda

skedda_list_bookings

Read-onlyIdempotent

List bookings in the user's own Skedda account from ChatGPT, Claude or any AI agent. Returns how to do it in Skedda step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Skedda Cloud Browser. Skedda's official API: Skedda has a read-only API in beta and no official MCP server (checked 31 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": "skedda_list_bookings"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds that the tool opens nothing by itself and returns structured step instructions, plus useful context about Skedda's API status.

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 description is only three sentences, but the first sentence is misleading and includes extraneous phrasing like "from ChatGPT, Claude or any AI agent." The crucial clarification appears second rather than being front-loaded, and the API-check date is not needed for invocation.

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 guide tool with no output schema, the description adequately covers what it returns (step-by-step screens, buttons, and fields) and confirms it has no side effects. It also points to the cotlet_browser_* tools for execution, which completes the expected workflow.

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 has zero parameters and an empty object schema, so there are no parameter semantics for the description to clarify. This matches the baseline of 4 for a no-parameter tool.

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 opens with "List bookings" but then says the tool "Returns how to do it in Skedda step by step ... and opens nothing by itself," shifting the actual function from data retrieval to instruction generation. That distinction is disclosed, but the mismatch with the tool name and title makes the real purpose less immediately clear than it should be.

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 explains the workflow clearly: call this tool to get step-by-step screens/buttons/fields, then execute with the cotlet_browser_* tools. It does not specify when to choose this over all siblings, but the intended sequence and alternative tool family are stated.

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

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