Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get discount

get_discount
Read-only

Retrieve full details for a single discount by ID or code, including type, value, currency, minimum subtotal rules, usage limits, and validity window.

Instructions

Get one discount's full details by id or code: type, value, currency, minSubtotal (default currency, or a fixed code's own), minSubtotalByCurrency (per additional currency), usage limits and validity window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idOrSlug": "<idOrSlug>"
    },
    "name": "get_discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
idOrSlugYesThe discount's id or code (from list_discounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "idOrSlug"
      +]
  2. First observedv0.73.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds real value by enumerating the returned payload (type, value, currency, min subtotals, usage limits, validity window), which is important since there is no output schema; it does not cover not-found or permission behavior, keeping it below a 5.

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?

One sentence, front-loaded with the verb and resource, followed by the returned field groups. It is dense but every clause carries information; the parenthetical clarifications about minSubtotal currencies are slightly compressed but not wasteful.

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?

For a single-parameter read tool with full schema coverage and no output schema, the description covers the key input (id or code) and enumerates the return fields an agent would need to plan next steps. Nothing essential to calling it correctly is missing.

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 coverage is 100% and the schema already documents idOrSlug as 'the discount's id or code (from list_discounts)'. The description repeats the id-or-code duality without adding format, casing, or fallback semantics, so it lands at the baseline for a fully documented single parameter.

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 names a specific verb and resource ('Get one discount's full details') and constrains the scope to a single record, so it is clearly distinct from a list or mutation tool. It stops short of explicitly naming which sibling to use instead for listing or filtering, but the singular scope is unambiguous.

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 states the lookup key ('by id or code'), which tells the agent what input form is accepted, and the schema points to list_discounts as the source of that key. There is no explicit when-to-use/when-not guidance or mention of the create/update/set_discount_enabled siblings, so usage is only implied.

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