Skip to main content
Glama
AbbottDevelopments

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

list_labor

Retrieve labor line items for a specific service within a work order. Provide the order ID and service ID to get the list.

Instructions

List the labor line items on a service. Shopmonkey nests labor under order > service, so both orderId and serviceId are required — call list_services with an orderId first to get the serviceId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe work order ID the service belongs to
serviceIdYesThe service ID to list labor line items for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.1
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Maximum number of results to return (default: 25)",
-  "type": "number"
-}
    • 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 labor entries by work order ID"New value: +"The work order ID the service belongs to"
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number for pagination (default: 1)",
-  "type": "number"
-}
    • addedInput schema / properties / serviceId
      Added value: +{
+  "description": "The service ID to list labor line items for",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "orderId",
+  "serviceId"
+]
  2. First observedv1.0.0

TDQS

A5/5.0
Behavior5/5

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

The verb 'list' unambiguously implies a read-only operation with no side effects, conveying the behavioral profile effectively.

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?

Two concise sentences deliver all necessary information without any fluff or redundancy.

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

Completeness5/5

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

The description covers the object being operated on, the required parameters, and the prerequisite action, making it self-sufficient for the agent.

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

Parameters5/5

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

Both orderId and serviceId have clear descriptive definitions that explain their roles in the operation.

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?

Clearly states the tool lists labor line items on a service, with the specific context of Shopmonkey's nesting under order > service.

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

Usage Guidelines5/5

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

Provides a direct prerequisite hint to call list_services first to obtain the serviceId, which is practical usage guidance.

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

Install Server

Other Tools