Skip to main content
Glama

list_booking_links

The user's booking links with their public URLs and every setting (weekly hours in each link's timezone tz, slug, length, location, notice, window, buffer, daily cap, end date, the booking form's questions, reminder emails, routines that block, the Google account, and hosts for a team link), and upcoming bookings made through them. On a team link some hosts may have their own weekly hours (hosts.host_hours, each in its own tz): with mode "any" that host is offered only in those hours, with "all" they narrow the link's; the link's days/from/to don't change them, and they're set in the Caddie app. Also lists teammates' team links the user hosts, or sees as a workspace owner or admin (made_by, can_edit: false: only their maker changes them). Read only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it declares 'Read only,' lists the returned setting categories, explains team-link host-hour semantics, and clarifies workspace-owner/admin visibility and can_edit:false permissions. It does not mention pagination, sorting, or response-size behavior, so it is strong but not exhaustive.

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 front-loads the main resource, but the first sentence is a long run-on containing nested parentheticals and setting lists. The information is useful, yet the dense semicolon structure makes it harder to scan than it should be for a simple list operation.

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?

Given zero parameters, no output schema, and no annotations, the description is fairly complete: it covers what is returned, team-link host-hour behavior, and permission boundaries. It still lacks details about pagination, ordering, or how upcoming bookings are bounded, which keeps it from a 5.

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 no parameters, so there is no parameter semantics to compensate for. The schema has zero properties and 100% coverage by definition; a baseline 4 is appropriate for a zero-parameter tool whose description focuses on outputs and permissions.

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 identifies the resource: the user's booking links, their public URLs, settings, and upcoming bookings made through them. It also distinguishes read-only listing from the create/update/delete booking-link siblings via 'Read only.' It stays a noun-phrase description rather than an explicit 'List ...' verb, which keeps it just below the top score.

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?

It explains scope details like teammate visibility and team-link host hours, but it never explicitly says when to use this tool versus create_booking_link, update_booking_link, delete_booking_link, or disable_booking_link. The read-only nature is implied, yet there is no direct usage-routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources