Skip to main content
Glama

save_loyalty_program

Destructive

Create or update the loyalty programme. Use revision 0 to create or the current revision to edit. Spend per point is in minor units of the programme currency.

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": {
      "currency": "<currency>",
      "spendPerPoint": "<spendPerPoint>",
      "rewardName": "<rewardName>",
      "rewardPoints": "<rewardPoints>",
      "enabled": "<enabled>",
      "revision": "<revision>"
    },
    "name": "save_loyalty_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
currencyYes
revisionYes
rewardNameYes
rewardPointsYes
spendPerPointYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/safety profile is covered. The description adds real behavioral value with the revision-based create-vs-edit protocol and the minor-units convention for spendPerPoint. However, for a tool flagged destructive, it says nothing about what is overwritten or destroyed — e.g. whether an edit replaces the whole programme definition or affects existing member point balances.

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 the action, then the revision protocol, then the unit convention. Nothing is repeated from the schema or annotations, and every sentence adds new information.

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 six-parameter, all-required, destructive upsert with no output schema, the description covers the create/edit distinction and one unit convention but omits critical context: the effect of an update on existing programme data, and what the remaining four parameters represent. It is usable but not sufficient for confident invocation.

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 all six required parameters. It only explains two: revision (0 creates, current edits) and spendPerPoint (minor units of programme currency). The meaning of currency, rewardName, rewardPoints, and enabled is left to be inferred from parameter names, which is a partial gap for a 0%-coverage schema.

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 opens with a specific verb pair and resource: 'Create or update the loyalty programme.' That distinguishes it clearly from the read-only sibling get_loyalty_program without having to name it. It does not explicitly call out that sibling, which keeps it just short of a 5.

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 explicitly tells the agent how to choose between the two modes: 'Use revision 0 to create or the current revision to edit.' That is genuine routing guidance for an upsert tool. It does not state prerequisites (e.g. where to obtain the current revision) or any when-not-to-use condition.

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