Skip to main content
Glama
AbbottDevelopments

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

list_canned_services

Retrieve a paginated list of canned service templates from Shopmonkey, optionally filtered by location ID.

Instructions

List pre-built canned service templates from Shopmonkey. These are reusable service templates that can be added to work orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 25)
locationIdNoFilter by location ID. Defaults to SHOPMONKEY_LOCATION_ID env var if set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
+}
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It states the operation lists templates but does not mention that it is read-only, pagination behavior, or that it returns a list. Basic but not exhaustive.

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 sentences with no redundant wording. It efficiently conveys the purpose and nature of the templates.

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 list operation, the description gives sufficient context about what the tool does and the nature of the items. It does not explain return format, but that is acceptable without an output schema.

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 schema provides descriptions for all three parameters (skip, limit, locationId), so coverage is 100%. The description adds no extra parameter context, so baseline of 3 is appropriate.

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 verb 'List' and the resource 'pre-built canned service templates from Shopmonkey', adding context that these are reusable templates for work orders. This is specific and unambiguous.

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 does not explicitly contrast with sibling tools like get_canned_service or create_canned_service. While it implies a listing operation, it lacks direct guidance on when to choose this over alternatives.

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