Skip to main content
Glama
Sign In
@aiwerk/mcp-server-cal

@aiwerk/mcp-server-cal

Official
by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cal_list_bookings

List bookings with optional filters by status, event type, date range, and limit to retrieve specific booking records.

Instructions

List bookings with optional filters. Optional: status (upcoming|recurring|past|cancelled|unconfirmed), eventTypeId, dateFrom (ISO 8601), dateTo (ISO 8601), limit.

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

Input Schema

NameRequiredDescriptionDefault
statusNo
eventTypeIdNo
dateFromNo
dateToNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions optional filters but does not disclose default behavior (e.g., which bookings are returned if no filters applied), ordering, pagination beyond the limit parameter, authentication needs, or side effects. This is insufficient for a listing tool.

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?

Two short sentences with no fluff. The first sentence states purpose, the second lists filters. Every word carries meaning, and it is front-loaded with the core action.

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 5 parameters, no output schema, and no annotations, the description is too minimal. It omits return format, default sorting, default status filter, and error conditions. For a listing tool with multiple filters, more context is needed to guide the AI 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 description coverage is 0%, so the description compensates by listing the parameters and their meanings: status with enum values, eventTypeId, dateFrom/dateTo as ISO 8601, and limit. It adds value beyond the raw schema but lacks details like what eventTypeId refers to or default limit (though schema says 20). It is adequate but not thorough.

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 'List bookings with optional filters,' identifying the resource (bookings) and action (list). It lists filter parameters, which distinguishes it from sibling tools like cal_get_booking (single booking) or cal_list_event_types (different resource). However, it does not explicitly differentiate from siblings.

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

Usage Guidelines3/5

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

The description tells when to use the tool (to list bookings with filters) but does not specify when not to use it or mention alternatives like cal_get_booking for a single booking. No exclusions or context about prerequisites are provided.

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

Deploy Server

Other Tools