Skip to main content
Glama

create_appointment

Idempotent

Create a requested appointment for a saved contact. Times are Unix milliseconds. Reuse the same idempotency key when retrying.

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": {
      "contactId": "<contactId>",
      "start": "<start>",
      "end": "<end>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
titleNo
suburbNo
addressNo
contactIdYes
serviceIdNo
assigneeIdNo
locationIdNo
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, readOnlyHint=false, and destructiveHint=false, and the description usefully explains the retry contract that pairs with idempotency. However, it says nothing about what "requested" status implies, what happens on duplicate submissions, or what permissions are needed.

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?

Three short sentences, zero filler, with the core action and the time-format caveat front-loaded before the retry note.

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?

No output schema exists and annotations are thin, so the description should do more for a 10-parameter mutation: it omits return shape (e.g., the new appointment ID), status semantics, and half the fields. It does cover the two highest-risk gaps, timestamp format and idempotent retries.

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?

Schema description coverage is 0% across 10 parameters, so the description must carry the load, and it only clarifies start/end units (Unix milliseconds), contactId's "saved contact" constraint, and the idempotencyKey semantics. Six parameters (title, suburb, address, serviceId, assigneeId, locationId) receive no meaning whatsoever.

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?

Specific verb plus resource ("Create a requested appointment") with a stated precondition ("for a saved contact"). It does not distinguish itself from siblings like reschedule_appointment or create_class_sessions, so an agent must still infer which creator to pick.

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 Precondition "for a saved contact" and the retry instruction ("Reuse the same idempotency key when retrying") give implied usage context. There is no explicit when-not guidance and no named alternative for rescheduling or cancelling an existing appointment.

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