Skip to main content
Glama

list_appointment_services

Read-onlyIdempotent

List saved services with appointment duration, buffer, staff and resource assignments, online booking availability, and on-site service postcodes.

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

Input Schema

NameRequiredDescriptionDefault
bookableOnlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the useful behavioral fact that results carry rich per-service configuration (buffers, staff/resource assignments, booking availability), but says nothing about pagination, result volume, or ordering for what is likely a multi-record list.

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

Conciseness4/5

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

One sentence, front-loaded with the verb and resource, with zero hedging or filler. The trailing field enumeration is dense but each item earns its place given there is no output schema.

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

Completeness3/5

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

Because there is no output schema, describing the returned fields is genuinely valuable and partially compensates. However, for a list tool with one undocumented filter parameter and no pagination or result-size guidance, the definition leaves an agent unsure how to narrow results or how large a response to expect.

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

Parameters2/5

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

The single parameter bookableOnline has 0% schema description coverage, and the description never mentions it, so nothing explains that the list can be filtered to only online-bookable services. The phrase 'online booking availability' refers to a returned field, not the input filter, which risks being read as return-value prose rather than filter semantics.

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?

States a specific verb and resource ("List saved services") and then enumerates the returned attributes: appointment duration, buffer, staff/resource assignments, online booking availability, and on-site postcodes. That is far clearer than a tautology, but it never distinguishes this from the adjacent sibling list_business_services, so the agent cannot tell which 'services' list it needs from the description alone.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named despite list_business_services being an obvious candidate for confusion. The only usage signal is the imperative 'List', which is implicit at best.

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