Skip to main content
Glama
AbbottDevelopments

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

list_locations

Retrieve all shop locations and their IDs to filter resources by shop in multi-location operations.

Instructions

List all shop locations in Shopmonkey. Useful for multi-location shops to identify location IDs for filtering other resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination (default: 0)
limitNoMaximum number of results to return (default: 25)

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

A4.3/5.0
Behavior4/5

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

The verb 'List' implies a read-only operation, but no explicit mention of side effects or side effects absence. Given no annotations, it's reasonably transparent but could be more explicit about non-destructiveness.

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 with no fluff, front-loading the primary purpose and then adding context.

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?

Provides sufficient context for when it would be used and why the returned location IDs matter. No output schema is provided, but the description covers the essential purpose.

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?

Schema covers both parameters with descriptions. Description adds no extra meaning beyond the schema, so baseline 3 applies.

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 it lists all shop locations, with a specific verb and resource. Unambiguous and distinct from any sibling tool.

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?

Provides a concrete use case (multi-location shops needing location IDs for filtering), though it doesn't explicitly state when not to use it or contrast with 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