Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List discounts

list_discounts
Read-only

List discount codes in a workspace and filter by enabled status, type, or code search; use offset paging while hasMore is true to retrieve all results.

Instructions

List discount codes in the workspace. Filter by enabled, type, or a code search; page on with offset while hasMore is true.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
offsetNo
searchNoSubstring match on the code
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.146.2
    • changedInput schema / properties / offset / 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: -25
    • removedInput schema / properties / offset / default
      Removed value: -0
  3. First observedv0.73.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value by disclosing the response-side pagination contract ('while hasMore is true'), which is not in any structured field since no output schema exists. It stops short of describing what a discount record contains or any ordering/default-page-size behavior.

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 sentences, zero waste, with the resource scope front-loaded ahead of filtering and paging mechanics. Every clause maps to an actionable detail.

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?

For a simple, zero-required-parameter list tool this covers the essentials: what is listed, how to narrow it, and how to page. Given the absence of an output schema, it should ideally say more about the shape of returned discount records and the page size default behind `limit`.

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 only 20% (only `search` is documented), so the description has to carry weight. It does clarify the three filter axes (enabled, type, code search) and confirms `offset` is the paging parameter, but `limit` is never mentioned and no defaults or ranges are given, leaving a real gap.

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?

The description opens with a specific verb and resource ('List discount codes in the workspace'), making the target collection unambiguous against the many other list_* siblings that operate on products, orders, price lists, etc. It lacks an explicit statement contrasting it with the nearest-sounding siblings such as list_price_lists, but the resource name does most of the disambiguating work.

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?

It gives usable invocation guidance: filter by enabled, type, or code search, and paginate with offset while hasMore is true. However, there is no when-to-use vs when-not guidance and no explicit alternative named, so an agent must infer the selection logic.

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