Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_canned_service

Create reusable service templates for work orders, configuring pricing model, express, bookable, recommended, and location settings.

Instructions

Create a new canned service template in Shopmonkey. Canned services are reusable service bundles that can be added to work orders.

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_canned_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the canned service (e.g., "Full Synthetic Oil Change")
expressNoWhether this is an express service
lumpSumNoWhether to display as a single lump-sum price on the work order
pricingNoPricing model: FixedPrice uses fixedPriceCents; LineItem sums its line items
bookableNoWhether customers can book this service online
locationIdNoLocation ID to associate the service with. Defaults to SHOPMONKEY_LOCATION_ID env var if set.
descriptionNoDescription of the service
recommendedNoWhether to show this as a recommended service
fixedPriceCentsNoFixed price in integer cents (e.g., $59.99 = 5999). Only applicable when pricing is FixedPrice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic create action and defines canned services; it does not mention that this is a mutating operation, potential side effects, permission requirements, or response format. Critical 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 two concise sentences: the first states the action and scope, the second provides essential context about what canned services are. It is front-loaded with the action and contains zero fluff or redundancy.

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?

Given the tool's complexity (9 parameters) and absence of an output schema, the description provides adequate context about the purpose and domain but omits details on return values, prerequisites, or behavioral expectations. It is minimal and leaves the agent to infer how the creation result is handled.

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?

The input schema provides 100% parameter coverage with detailed descriptions for each of the 9 parameters. The tool description adds no additional parameter semantics beyond the schema, so it meets the baseline for high schema coverage. No value beyond schema is added.

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), the resource (canned service template), and the domain (Shopmonkey). It defines canned services as reusable bundles, distinguishing it from update/delete siblings. The purpose is unambiguous and specific.

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 makes clear this is for creating new templates, which implies when to use it, but it does not explicitly exclude alternatives or mention conditions like updating existing templates. The context is clear but lacks explicit when-not guidance or alternative references.

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

Deploy Server

Other Tools