Meridian

Get Discount

discount_get

Read-only

Returns one Plan Builder discount. discount_id is resolved in order: uuid, then app-local handle, then merchant-entered code (case-insensitive). 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>",
      "discount_id": "<discount_id>"
    },
    "name": "discount_get"
  }
}

Input Schema

Name	Required	Description
`app_id`	Yes	The app uuid returned by `apps_list`.
`discount_id`	Yes	Discount uuid, handle, or code from `discounts_list`.
`organization_id`	No	An 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.

First observedNov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description does add real behavior absent from the annotations: the precedence order uuid > handle > code and case-insensitive matching. That is useful but narrow, and it says nothing about not-found behavior or lookup performance.

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?

Three short sentences, front-loaded with what is returned and followed by the identifier resolution rule. Every clause carries information, with no filler or redundancy.

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?

For a read-only single-record lookup with full schema coverage, the definition covers identity, lookup semantics, and the source of app_id. Because there is no output schema, the absence of any hint about the returned discount's fields leaves a small gap, which is minor for a simple get.

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?

Schema coverage is 100%, so the schema alone documents all three parameters. The description goes beyond it by specifying the resolution order among the three accepted identifier forms and that code matching is case-insensitive, which the schema does not state.

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 states a specific verb and resource ("Returns one Plan Builder discount") and the singular "one" implicitly sets it apart from a list tool such as discounts_list. It does not name any alternative, so differentiation from siblings is left to inference.

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: an agent can tell this is the single-record fetch versus a list, and the mention of apps_list tells it where app_id originates. There is no explicit statement of when to prefer this tool over a sibling or of any preconditions beyond that.

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

All Meridian tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?