Skip to main content
Glama
AbbottDevelopments

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

list_orders

Fetch work orders from Shopmonkey with filters for status, customer, location, and pagination to retrieve relevant records.

Instructions

List work orders from Shopmonkey. Filter by status, customer ID, date range, or location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 25)
statusNoFilter by order status
customerIdNoFilter orders by customer ID
locationIdNoFilter by location ID (for multi-location shops). Defaults to SHOPMONKEY_LOCATION_ID env var if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.1
    • 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"
+}
    • changedInput schema / properties / status / description
      Previous value: -"Filter by order status (e.g., estimate, work_order, invoice)"New value: +"Filter by order status"
    • addedInput schema / properties / status / enum
      Added value: +[
+  "Estimate",
+  "RepairOrder",
+  "Invoice"
+]
  2. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

The word 'List' implies a read-only operation, but with no annotations and no mention of side effects, pagination behavior, or response shape, the behavioral transparency is average. It does not contradict any annotations because none are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it includes an inaccurate reference to date range filtering that is not supported by the schema. It is short and front-loaded but not entirely accurate.

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?

With no output schema and no annotations, the description is thin. It gives the basic purpose and filter hints, but omits pagination defaults, result shape, and the fact that date range filtering is not actually available. An agent could be misled into expecting a date range parameter.

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

Parameters2/5

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

The schema descriptions fully cover the parameters, so the baseline is 3, but the description adds no extra value beyond the schema and introduces a misleading 'date range' filter that does not exist in the input schema. This detracts from clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states a specific verb and resource: 'List work orders from Shopmonkey.' This distinguishes it from single-order tools like get_order and mutation tools like create_order/update_order. Minor deduction because the description mentions filtering by date range, but no date range parameters exist in the schema.

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

Usage Guidelines3/5

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

The description implies this tool is for listing multiple work orders, and the name contrasts with get_order, but it does not explicitly state when to use this tool versus alternatives. No when-not or alternative guidance is provided.

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