Shopmonkey MCP Server

create_order

Create a new work order for a vehicle and customer, setting its status and location.

Instructions

Create a new work order 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_order"
  }
}

Input Schema

Name	Required	Description
`name`	No	Order title shown on the work order (e.g. "Front brake job")
`status`	No	Initial order status
`vehicleId`	No	Vehicle ID to associate with the order
`customerId`	No	Customer ID to associate with the order
`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.

Changed3 schema fields changedv1.1.1Sep 8, 2026

addedInput schema / properties / name

Added value: +{
+  "description": "Order title shown on the work order (e.g. \"Front brake job\")",
+  "type": "string"
+}

changedInput schema / properties / status / description

Previous value: -"Initial order status (e.g., estimate, work_order)"New value: +"Initial order status"

addedInput schema / properties / status / enum

Added value: +[
+  "Estimate",
+  "RepairOrder",
+  "Invoice"
+]

First observedv1.0.0Mar 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that the tool creates a new order, which implies a write operation. With no annotations to indicate side effects, this basic behavioral transparency is sufficient for the simple action, though it does not detail any potential implications (e.g., defaults or related records).

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, focused sentence that directly states the purpose without any unnecessary words or tangential details. It is concise and front-loaded.

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

Completeness4/5

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

For a simple create operation with no output schema, the description is complete. It correctly identifies the action and object, and the schema provides all necessary parameter details. No critical context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides descriptions for all five parameters, covering 100% of them. The individual descriptions (e.g., locationId default) add clear meaning, so the tool description itself does not need to elaborate further.

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 action ('Create a new work order') and the context ('in Shopmonkey'), making the tool's purpose unambiguous and easily distinguishable from sibling tools that operate on other resources (e.g., customers, vehicles).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly mention when to use this tool versus alternatives, but since there is no other create-order tool among the siblings, the usage context is implicit. The clear purpose provides sufficient guidance for an agent to select it appropriately.

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

Deploy Server