Retrieve shop users and technicians from Shopmonkey, with optional pagination and location filtering to manage staff lists.
List shop users and technicians from Shopmonkey.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | Number of records to skip for pagination (default: 0) | |
| limit | No | Maximum number of results to return (default: 25) | |
| locationId | No | Filter by location ID. Defaults to SHOPMONKEY_LOCATION_ID env var if set. |
Changes observed during successful MCP inspections.
v1.1.1Input schema / properties / pageRemoved value: -{
- "description": "Page number for pagination (default: 1)",
- "type": "number"
-}Input schema / properties / skipAdded value: +{
+ "description": "Number of records to skip for pagination (default: 0)",
+ "type": "number"
+}v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description relies on 'List' to imply read-only behavior, but it does not explicitly mention side effects, authorization, or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, front-loaded sentence; concise and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description plus schema is sufficient for a simple list operation, though no output shape is described; not a major gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All three parameters are documented in the schema with descriptions and defaults; the description adds no extra semantic detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states the verb ('List') and resource ('shop users and technicians') clearly, but does not explicitly differentiate from sibling tools like get_user.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool instead of get_user or other list tools; the only implication is from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.