Skip to main content
Glama

Use a rebate

evuun_rebate_use
Idempotent

Use the signed-in person's EVUUN rebate on one item before payment (apply, with amount_minor), or take it back (release). Hotels use EVUUN member prices and never take a rebate; the answer says so. Reuse the idempotency key on retry.

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": {
      "action": "<action>",
      "arrangement_id": "<arrangement_id>",
      "item_id": "<item_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "evuun_rebate_use"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
item_idYes
amount_minorNo
arrangement_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description earns credit for additions: the apply/release distinction, the requirement to pass amount_minor on apply, the hotel exemption, and the operational instruction to reuse the idempotency key on retry. It does not describe what happens if the amount exceeds the available rebate or what a successful apply returns, which is the remaining gap for a mutation tool.

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?

Three sentences, front-loaded with the primary action and its parameter before the exclusion and the retry note. Nearly every clause earns its place, though the phrasing 'the answer says so' is loose and slightly ambiguous about what the response actually contains.

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 non-destructive, idempotent mutation with no output schema and zero schema descriptions, the description covers the main flow, the optional-parameter condition, and retry behavior. It still omits failure modes (insufficient rebate balance, already-applied rebate, item not in the arrangement) that an agent would need to handle correctly.

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 0%, so the description must carry parameter meaning, and it covers action values, amount_minor's role on apply, and idempotency-key reuse. It says nothing about arrangement_id or item_id beyond 'one item', leaving two of five parameters explained only by their patterns; partial compensation justifies a 3 rather than higher.

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 uses a specific verb and resource ('use ... rebate') and enumerates both modes, apply and release, with the key qualifier 'on one item before payment'. That is enough to distinguish it from a plain rebate-inspection sibling like evuun_rebate, though it never names or contrasts an alternative directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear timing condition ('before payment') and an explicit exclusion: hotels use member prices and never take a rebate, so the call should not be made there. It stops short of naming a fallback tool or stating what to do when the exclusion applies, which keeps it below a 5.

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