Shopmonkey MCP Server

create_appointment

Book new appointments in Shopmonkey by specifying customer, vehicle, time slots, and service details to schedule automotive service visits.

Instructions

Book a new appointment in Shopmonkey.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_appointment"
  }
}

Input Schema

Name	Required	Description
`notes`	No	Additional notes for the appointment
`title`	No	Appointment title or summary
`endDate`	No	Appointment end date/time (ISO 8601 format)
`orderId`	No	Work order ID to link to
`startDate`	No	Appointment start date/time (ISO 8601 format)
`vehicleId`	No	Vehicle ID for the appointment
`customerId`	No	Customer ID for the appointment
`locationId`	No	Location ID for multi-location shops. Defaults to SHOPMONKEY_LOCATION_ID env var if set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, forcing the description to carry full disclosure burden. However, it reveals nothing about side effects, conflict handling (e.g., double-booked slots), return values, or whether notifications are sent. Only states the basic creation action.

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?

Single sentence with zero redundancy. However, for an 8-parameter creation tool with zero annotations, this brevity may be insufficient rather than optimally concise—it leaves critical context unstated.

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?

Inadequate for complexity level. An 8-parameter mutation tool with no annotations and no output schema requires substantial contextual support (prerequisites, side effects, required relationships). The single-sentence description fails to provide this.

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?

With 100% schema description coverage, the schema adequately documents all 8 parameters (customerId, vehicleId, etc.). The description adds no semantic detail beyond the schema, but baseline 3 applies per rubric for high-coverage schemas.

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 uses a specific verb ('Book') with clear resource ('appointment') and context ('Shopmonkey'). It clearly distinguishes from siblings like 'get_appointment', 'update_appointment', and 'list_appointments' by indicating this is a creation operation.

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?

No guidance provided on when to use this versus 'update_appointment' or prerequisites (e.g., that customerId/vehicleId likely require existing records). No mention of required fields despite all 8 parameters being technically optional in the schema.

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

Deploy Server