Skip to main content
Glama

list_booking_schedules

Read-onlyIdempotent

List staff or resource schedules, their current revisions and the business time zone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "list_booking_schedules"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results carry current revisions and the business time zone, which is useful return-context, but it says nothing about ordering, pagination, or permissions.

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?

A single front-loaded sentence with zero filler: verb, resource, enum values and returned fields all in one clause chain. Nothing to cut and nothing buried.

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?

For a simple, read-only, one-parameter list tool with no output schema, the description covers what it returns (schedules, current revisions, business time zone) and the staff/resource distinction. It stops short of pagination or result-size behavior, which is the only real gap for a listing endpoint.

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 must compensate. It does map the single 'kind' enum conceptually to 'staff or resource', giving the values meaning, but it does not state that the parameter is required or explain how results differ between the two kinds. Partial compensation only.

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 (list) and resource (booking schedules) and clarifies the scope: staff or resource schedules. It also hints at what is returned. It does not name a sibling it is not – e.g., save_booking_schedule or get_booking_availability – but the 'list' verb and read-only framing make the read/write split with save_booking_schedule evident.

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?

Usage is only implied by the verb 'List'; there is no explicit statement of when to pick this over get_booking_availability or save_booking_schedule, and no stated prerequisites. An agent can infer this is the retrieval path for schedules, but nothing in the text confirms it.

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