Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List carts

list_carts
Read-only

Retrieve shopping carts in an admin view, filtered by status and paginated, to monitor active, abandoned, or ordered carts and their total values.

Instructions

List shopping carts (admin view) with optional status filter and pagination. totalValue is in minor units. channel is the key of the sales channel the cart was started on (null for none): a buyer has one active cart per channel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_carts"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.146.2
    • changedInput schema / properties / skip / minimum
      Previous value: --9007199254740991New value: +0
  2. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / default
      Removed value: -20
    • removedInput schema / properties / skip / default
      Removed value: -0
  3. First observedv0.73.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: admin-view scoping, minor-unit currency values, and the invariant that a buyer has one active cart per channel, which an agent would not know from the structured fields alone.

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

Conciseness4/5

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

Three short sentences, front-loaded with purpose and scope before the field notes; nothing is redundant. The field-semantics sentence is dense but each clause carries information an agent cannot get elsewhere.

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

Completeness3/5

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

With no output schema, the description carries the return-value burden and covers only two fields (totalValue, channel), leaving the list envelope, item shape, and pagination behavior unexplained. It also omits any auth/permission context for the admin view beyond the label.

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 description coverage is 0%, so the description must compensate, and it only partially does: it confirms that status filtering and pagination are optional but never explains skip/limit defaults, ordering, or the unusual negative minimum allowed on limit. It also spends two sentences on output field meanings rather than the parameters.

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?

States a specific verb and resource ('List shopping carts') and scopes it as an admin view with optional status filtering and pagination. It is clearly distinguishable from the destructive sibling delete_carts, though it does not explicitly name any alternative list tool.

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 phrase 'optional status filter and pagination' implies when the tool is used (browsing/auditing carts, optionally narrowing by status), but there is no explicit when-to-use, when-not, or named alternative guidance. The '(admin view)' hint signals an audience but not exclusions.

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

Deploy Server

Other Tools