Skip to main content
Glama

List Discounts

discounts_list
Read-onlyIdempotent

Lists an app's Plan Builder discounts: discount_id, handle, code, name, description, status, type, value, duration fields, plan restrictions, availability, redemption limits, and timestamps. Takes the app_id returned by apps_list.

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": {
      "app_id": "<app_id>"
    },
    "name": "discounts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app this call works on: its `app_id` uuid from `apps_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app uuid returned by `apps_list`."New value: +"The app this call works on: its `app_id` uuid from `apps_list`."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by enumerating the returned fields (status, duration, plan restrictions, availability, redemption limits, timestamps), which compensates for the absent output schema. It stops short of mentioning pagination, result size, or ordering, which keeps it from 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?

Two sentences, front-loaded with purpose and followed by return contents and the prerequisite call. The field enumeration is dense but earns its place given there is no output schema; a compact grouped phrasing would be slightly tighter but nothing is wasted.

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 read-only list tool with full schema coverage and clear annotations, the definition covers purpose, inputs and return shape adequately. It is incomplete on the operational details an agent may still need: pagination, result volume, ordering, and whether there is a companion single-discount retrieval tool.

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 100%, so both parameters are already documented in the schema, establishing a baseline of 3. The description only reinforces `app_id` provenance from `apps_list` and says nothing about `organization_id` or the slug-vs-uuid resolution it enables, so it adds little beyond the structured fields.

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

Purpose5/5

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

Opens with a specific verb and resource: 'Lists an app's Plan Builder discounts', scoping it to a single app and a named feature area (Plan Builder). That is enough for an agent to distinguish it from the other list tools in the catalog without opening the schema.

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 second sentence gives a prerequisite: it 'Takes the `app_id` returned by `apps_list`', which usefully chains it to the discovery tool. However, there is no explicit when-to-use versus when-not guidance, and no statement about what to do when the app has no discounts or how to fetch a single discount by id.

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.

Resources