Skip to main content
Glama

Little Works

get_booking_slots

Open booking times via booking APIs.

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_booking_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdNo
scheduleSlugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: no auth requirements, no indication whether slots are held or merely read, no rate limits, no side effects. "Open booking times" is genuinely ambiguous about whether the call mutates state, which is the single most important fact for an agent here.

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

Conciseness2/5

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

It is short, but brevity here comes from under-specification rather than efficiency. The one clause spends words on "via booking APIs" while omitting everything an agent needs, so nothing is effectively front-loaded.

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

Completeness1/5

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

With two undocumented parameters, no annotations, and no output schema, the description should explain parameter meaning and side-effect profile. It supplies neither, leaving the definition insufficient for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0% and the description never mentions serviceId or scheduleSlug. An agent cannot tell what a "serviceId" identifies versus a "scheduleSlug", whether either is required to get meaningful results, or what formats they take. This is the worst case for the low-coverage rule.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description largely restates the name: get_booking_slots becomes "Open booking times." The verb "open" is ambiguous (does it create availability or read it?), and nothing distinguishes this from siblings like get_hold_status, get_booking_confirm_link, or create_booking. Only the trailing "via booking APIs" adds words, not meaning.

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?

There is no statement of when to call this tool, when not to, or which sibling to use instead. An agent must guess whether this is the availability-lookup step before create_booking or an unrelated operation. No prerequisites or sequencing guidance are present.

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