Skip to main content
Glama
Sign In
medusa-mcp

medusa-mcp

by trhonpavel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List customer groups

list_customer_groups
Read-only

Retrieve and search customer groups such as B2B or VIP segments, with pagination, to use in price lists and promotions.

Instructions

Customer groups (e.g. B2B, VIP) – used by price lists and promotions.

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_customer_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoNumber of records (max 200)
offsetNoRecords to skip (pagination)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only a domain definition and does not disclose pagination behavior, default result size, filtering behavior, or any permission constraints beyond what annotations provide.

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?

The description is a single short sentence with no filler. It is front-loaded with the entity definition, though the sentence is so minimal that it omits the tool's action entirely.

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?

For a list tool with q, limit, and offset parameters and no output schema, the description is missing the core action, filtering semantics, and pagination context. The annotations cover read-only safety, but the description does not give an agent enough to invoke or interpret results confidently.

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?

Schema description coverage is 67%, with the q search parameter undocumented in the schema. The description adds no meaning for q, limit, or offset, so it does not compensate for the coverage gap. An agent gets no help understanding what q searches or how pagination behaves.

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

Purpose2/5

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

The description defines what a customer group is (e.g. B2B, VIP) but never states the tool's action. It does not say it lists or retrieves customer groups, and it does not distinguish this tool from save_customer_group or delete_customer_group. The name and title carry the actual purpose, so the description itself is largely tautological domain context.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as list_customers or save_customer_group. The phrase 'used by price lists and promotions' describes the entity's domain role, not when an agent should call this listing tool.

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