Skip to main content
Glama

Ask for a live video call or a home visit, offering up to 3 of the open times.

request_appointment

Ask for a live video call or a home visit, offering up to 3 of the open times. A job with nothing uploaded switches to that kind and becomes priced by the mover. Re-posting replaces the offer until a time is agreed. Scope: jobs:write.

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": {
      "job_id": "<job_id>",
      "kind": "<kind>",
      "times": "<times>",
      "name": "<name>",
      "email": "<email>",
      "phone": "<phone>",
      "consent": "<consent>"
    },
    "name": "request_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameYes
noteNoOptional, up to 500 characters
emailYes
phoneYes7 to 15 digits
timesYesUp to 3 starts from GET /jobs/{id}/slots
job_idYesThe job id (ULID)
consentYesMust be true: we email about this booking

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses real side effects: re-posting replaces the existing offer until a time is agreed, and a job with nothing uploaded switches kind and becomes priced by the mover. It also names the required scope (jobs:write), which tells the agent about auth expectations. It stops short of saying what happens on success or how the counterparty is notified beyond the schema's consent note.

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?

Four short sentences with the core action front-loaded and the scope tag last; little waste. The sentence "A job with nothing uploaded switches to that kind" is vaguely worded, since "that kind" and "nothing uploaded" are not defined locally, costing some clarity.

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?

Given 8 parameters, 7 required, no output schema, and a mutation that changes pricing and job kind, the description covers the important side effects and auth scope. It does not explain the outcome of a successful request (confirmation, pending state) or the upload-state condition in concrete terms, leaving gaps for an agent handling edge cases.

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 63%, so several parameters (name, email, kind) are undocumented in the schema, and the description only partly compensates by explaining that times are open slots (max 3) and that kind is either a live video call or a home visit. It adds no meaning for name, email, phone, or job_id beyond what the schema already states. Baseline 3 is appropriate given the partial coverage gap.

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+resource ("Ask for a live video call or a home visit") and a scoping constraint ("up to 3 of the open times"), so the agent knows what the call produces. It never names the nearby alternatives (request_visit, request_booking, list_appointment_times), so sibling differentiation is left to inference even though the kind enum overlaps conceptually with a visit-request tool.

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: you must already have open times ("offering up to 3 of the open times"), and re-posting is described as a replacement, which hints at when to call it again. There is no explicit statement of when to prefer this over request_visit or request_booking, and no stated prerequisite step (e.g., fetching slots first) is spelled out in the description.

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