Ceki

get-schedules

Retrieves all bookings and scheduled sessions, with optional filtering by status (upcoming, completed, cancelled).

Instructions

List all your bookings and scheduled sessions.

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": "get-schedules"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Filter by booking status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only indicates a listing operation but fails to mention pagination, data scope (e.g., user-specific vs. all), or any side effects. The agent cannot infer the tool's safety or limitations from the description alone.

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

Conciseness5/5

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

The description is a single concise sentence that directly states the tool's purpose with no extraneous information. Every word earns its place, making it efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and the presence of a similar sibling ('get-my-bookings'), the description lacks sufficient context to distinguish the tool's exact function. It does not cover whether the output includes all timeframes, if filtering is mandatory, or how to interpret results, leaving gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single optional 'status' parameter, which already has a clear schema description. The tool description does not add any additional semantic meaning beyond what the schema provides, so baseline of 3 is appropriate.

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 clearly states the tool lists all bookings and scheduled sessions, using the specific verb 'list' and resource description. However, it does not distinguish itself from the sibling tool 'get-my-bookings', which likely serves a similar purpose, causing potential ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-my-bookings'. It lacks any context about prerequisites, filtering behavior, or when not to use it, leaving the agent uninformed about optimal invocation scenarios.

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