Shopmonkey MCP Server

update_appointment

Modify or reschedule existing appointments in Shopmonkey by updating details like date, time, customer information, and work order links.

Instructions

Update or reschedule an existing appointment.

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": {
      "id": "<id>"
    },
    "name": "update_appointment"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The appointment ID to update
`notes`	No	Additional notes
`title`	No	Appointment title or summary
`endDate`	No	New end date/time (ISO 8601 format)
`orderId`	No	Work order ID to link to
`startDate`	No	New start date/time (ISO 8601 format)
`vehicleId`	No	Vehicle ID for the appointment
`customerId`	No	Customer ID for the appointment

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. States mutation intent ('update') but lacks behavioral details: partial vs full replacement semantics, validation rules for parameter combinations (e.g., vehicleId/customerId consistency), idempotency, error handling for invalid IDs, or return value structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is efficient and front-loaded, wasting no words. However, for an 8-parameter mutation tool with zero annotations and no output schema, the description is inappropriately brief—undersized for the complexity rather than optimally concise.

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?

For a mutation tool with 8 parameters and no annotations/output schema, the description is insufficient. Lacks: explanation of partial update behavior, linking logic between orderId/vehicleId/customerId, return value documentation, and side effect disclosure.

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 has 100% description coverage, establishing baseline 3. Description adds minimal semantic context: 'reschedule' loosely implies date fields without explicitly mapping to startDate/endDate parameters. Does not explain parameter interactions or why only 'id' is required while other fields are optional.

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 specific verbs ('update', 'reschedule') and resource ('appointment'). Distinguishes from create_appointment by specifying 'existing' and from get/list tools by specifying mutation. However, does not clarify the relationship between 'update' and 'reschedule' (synonyms or distinct behaviors?) nor distinguish from sibling update tools (update_customer, update_vehicle).

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?

Implies prerequisite by stating 'existing appointment' but provides no explicit guidance on when to use this vs create_appointment, nor how to obtain the required ID (via get_appointment or list_appointments). No alternatives or prerequisites mentioned.

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

Deploy Server