intakeq-mcp

create_appointment

Create a new appointment in IntakeQ by providing all required booking details: practitioner ID, client ID, service ID, location ID, status, UTC date/time, email notification, and reminder type.

Instructions

Create a new appointment in IntakeQ. All fields are required.

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": {
      "PractitionerId": "<PractitionerId>",
      "ClientId": "<ClientId>",
      "ServiceId": "<ServiceId>",
      "LocationId": "<LocationId>",
      "Status": "<Status>",
      "UtcDateTime": "<UtcDateTime>",
      "SendClientEmailNotification": "<SendClientEmailNotification>",
      "ReminderType": "<ReminderType>"
    },
    "name": "create_appointment"
  }
}

Input Schema

Name	Required	Description
`Status`	Yes	Appointment status
`ClientId`	Yes	Client ID (integer)
`ServiceId`	Yes	Service ID
`LocationId`	Yes	Location ID
`UtcDateTime`	Yes	UTC date/time in Unix milliseconds
`ReminderType`	Yes	Reminder type
`PractitionerId`	Yes	Practitioner ID
`SendClientEmailNotification`	Yes	Whether to send client email notification

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that all fields are required, but that is already evident from the schema. It does not disclose side effects (e.g., whether creating an appointment triggers notifications, sends emails, or has irreversible consequences). The tool clearly performs a write operation, but additional behavioral context is missing.

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?

The description is a single concise sentence that immediately identifies the action and system. It is front-loaded and contains no redundant or irrelevant content. It fully maximizes conciseness, even if it lacks depth in other areas.

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

Completeness2/5

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

Given the absence of an output schema and annotations, the description is insufficient for a tool with 8 required parameters. It does not explain what the response looks like, what errors might occur, or any prerequisites. A create operation of this complexity needs more context to guide an agent toward correct invocation and result interpretation.

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 100%, with each parameter having a meaningful description. The tool description adds no additional parameter context beyond the schema. The statement 'All fields are required' merely repeats the 'required' array in the schema. Therefore, the description does not enhance parameter understanding beyond what is already structured.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Create a new appointment in IntakeQ.' The verb 'Create' and resource 'appointment' are specific, and it is distinct from sibling tools like update_appointment, get_appointment, and list_appointments. There is no ambiguity about what this tool does.

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?

The description offers no guidance on when to use this tool versus alternatives. It does not mention that update_appointment should be used for modifying existing appointments, nor does it note prerequisites such as having valid client, service, or practitioner IDs. A tool as complex as creating an appointment would benefit from explicit usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.