Skip to main content
Glama

list_coupons

Read-only

The coach's discount codes: code, % off, which plans it applies to (empty = all), redemptions vs limit, expiry and on/off.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 by structured data. The description adds what the record contains, including the non-obvious 'empty = all' semantics for the plan field, which is genuinely useful. It does not disclose volume, pagination, or whether inactive/expired coupons are included in the listing.

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?

A single dense sentence with the resource front-loaded and no filler. The telegraphic field list ('redemptions vs limit', 'on/off') is efficient but slightly ambiguous in phrasing, keeping it short of a 5.

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

Completeness4/5

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

With no parameters, no output schema, and read-only annotations, the description's main duty is to convey what comes back — and it enumerates the returned fields. Minor gaps remain around pagination and whether inactive coupons are included, but nothing essential for calling the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which establishes the baseline of 4. The description does clarify the meaning of a returned field ('empty = all' for plan applicability), adding interpretation value even though it applies to output rather than input.

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 identifies the resource precisely — the coach's discount codes — and enumerates the attributes surfaced (code, percent off, applicable plans, redemption counts vs limit, expiry, active flag). An agent can tell this apart from the many other list_* siblings because it names a distinct resource. It stops short of an explicit verb like 'list all', relying on the tool name to supply that.

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?

Usage is only implied: the agent infers this is the read path for retrieving coupons. There are no parameters, so no filtering alternatives exist, and no exclusions or prerequisites are stated. Adequate for a trivial no-arg list tool, but no explicit trigger conditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.