Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_services

List services for a specific work order by order ID. Use skip and limit to paginate results. Returns up to 25 services per request by default.

Instructions

List the services on a work order. Shopmonkey nests services under their order — there is no flat service list — so orderId is 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": {
      "orderId": "<orderId>"
    },
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 25)
orderIdYesThe work order ID to list services for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • removedInput schema / properties / locationId
      Removed value: -{
-  "description": "Filter by location ID. Defaults to SHOPMONKEY_LOCATION_ID env var if set.",
-  "type": "string"
-}
    • changedInput schema / properties / orderId / description
      Previous value: -"Filter services by work order ID"New value: +"The work order ID to list services for"
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number for pagination (default: 1)",
-  "type": "number"
-}
    • addedInput schema / properties / skip
      Added value: +{
+  "description": "Number of records to skip for pagination (default: 0)",
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "orderId"
+]
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the nesting behavior (services are nested under orders), which is useful structural context. However, it does not mention pagination behavior, response format, or any side effects. For a read-only list operation, this is somewhat minimal but not misleading.

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 front-loads the action and immediately explains the key constraint. There is no wasted verbiage, and the structure is clear and efficient.

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 list tool with pagination parameters and no output schema, the description provides enough context: it states the purpose, the required parameter, and the data model. It could optionally mention pagination defaults, but those are already in the schema. The description is complete enough for an agent to call the tool correctly.

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 schema already covers all three parameters (100% coverage), so the baseline is 3. The description adds semantic value by explaining why orderId is required and how the data is structured, which goes beyond the schema's simple field descriptions. This enhances the agent's understanding of the parameter's role.

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 lists services on a work order, with a specific verb, resource, and scope. It also explains the nesting context, which distinguishes it from other list tools in the sibling set. The purpose is unambiguous and differentiates it from tools like list_canned_services or list_labor.

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 explicitly states that orderId is required and explains why (services are nested under orders, no flat list). This gives clear context for when to use the tool and the necessary precondition. While it doesn't mention alternatives or when not to use, the guidance is adequate for this simple tool.

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