Skip to main content
Glama

Open times for a live video call or a home visit (`?kind=live|in_home`): inside

list_appointment_times
Read-only

Open times for a live video call or a home visit (?kind=live|in_home): inside the mover's hours, past their notice period, off their days off and clear of their booked appointments. Labels are in the mover's time zone. Scope: jobs:read.

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>",
      "job_id": "<job_id>"
    },
    "name": "list_appointment_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
job_idYesThe job id (ULID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real context: the four filtering rules that shape results, the time zone in which labels are rendered, and the required 'jobs:read' scope. It does not describe the shape of returned slots or how far ahead the window extends.

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?

Front-loaded with the resource and the two kinds, then the filtering rules, then scope — a sensible ordering with little filler. The embedded URL-style `?kind=live|in_home` fragment is the one piece of noise that does not earn its place.

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 two-parameter read tool with annotations and no output schema, the description covers the essentials: what is returned, how it is filtered, what time zone labels use, and what permission is needed. Only the return format and booking-window horizon are left implicit, which is acceptable given there is no output schema to lean on.

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 coverage is 50%: job_id is documented in the schema, while kind has only an enum. The description compensates for kind by spelling out that 'live' means a video call and 'in_home' a home visit, but the `?kind=live|in_home` query-string notation is a REST artifact that adds no semantic value for an MCP caller and could confuse.

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 ('Open times for a live video call or a home visit') and enumerates the two kinds the tool returns. It is clearly a read of bookable slots, but it never distinguishes itself from the sibling get_availability, which an agent could plausibly confuse it with.

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?

The description implies usage by defining what 'open' means (inside hours, past notice, off days off, no conflicts), which tells the agent the result is already filtered and needs no post-processing. However, it gives no explicit when-to-use/when-not guidance and names no alternative for the adjacent availability-lookup case.

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