Skip to main content
Glama

Little Works

list_appointments

List booking schedules.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden and discharges almost none of it. It says nothing about whether results are scoped to the caller's account, whether they include past or cancelled bookings, whether pagination or limits apply, or what shape the records take.

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 single sentence is front-loaded and free of waste, but it is under-specified rather than efficient — the whole budget is spent restating the name. One more clause about scope or return content would have cost little and added a lot.

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?

For a schema-less, annotation-less, output-schema-less list tool, the description is the only source of behavioral information, and it supplies none. An agent cannot predict scope, volume, or result structure before calling, which is a real gap for an enumeration tool.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter-level meaning is missing because no parameters exist.

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?

"List booking schedules" gives a verb plus a resource, but the resource is named inconsistently with the tool name (appointments vs booking schedules) and it does not distinguish this from nearby siblings such as get_appointment, get_booking_slots, or list_booking_services. An agent can guess it enumerates bookings, but cannot tell what it enumerates or how it differs from the slot/confirm-link tools.

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 when-to-use guidance at all: no statement of whose appointments are listed, no prerequisite, and no pointer to get_appointment for a single record or get_booking_slots for availability. The agent must infer the choice purely from tool names.

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