Skip to main content
Glama

set_mandate

Buyer: let your principal allow purchases without a payment link. They save a card with Stripe once (setup_url) and set a monthly budget and a cap per order; within them buy authorises the card on the seller's account at once and charges it only after the delivery arrived. Revocable any time with revoke_mandate.

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": {
      "monthly_budget_minor": "<monthly_budget_minor>"
    },
    "name": "set_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoyour key, if your client cannot send headers
purposeNooptional, one short sentence published with the signed mandate: what your agent buys (no personal data)
currencyNodefault chf; a mandate pays only listings in its own currency, and most listings are in CHF
max_order_minorNocap per order, default the smaller of budget and 50.00
monthly_budget_minorYesMonthly budget in Rappen/cents, e.g. 5000 for 50.00.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "your key, if your client cannot send headers",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / monthly_budget_minor / description
      Added value: +"Monthly budget in Rappen/cents, e.g. 5000 for 50.00."
  3. Changed1 schema field changed
    • addedInput schema / properties / currency / description
      Added value: +"default chf; a mandate pays only listings in its own currency, and most listings are in CHF"
  4. Changed1 schema field changed
    • removedInput schema / properties / currency / description
      Removed value: -"default chf; a mandate pays only listings in its own currency, and most listings are in CHF"
  5. Changed1 schema field changed
    • addedInput schema / properties / currency / description
      Added value: +"default chf; a mandate pays only listings in its own currency, and most listings are in CHF"
  6. Changed1 schema field changed
    • addedInput schema / properties / purpose
      Added value: +{
      +  "description": "optional, one short sentence published with the signed mandate: what your agent buys (no personal data)",
      +  "type": "string"
      +}
  7. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only supply the generic safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds substantive behavior: the card is saved once with Stripe via setup_url, the card is authorized on the seller's account immediately but charged only after delivery arrives, and the whole thing is revocable. The authorization-versus-charge timing is exactly the kind of escrow mechanic an agent cannot derive from structured fields.

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?

Two sentences, front-loaded with the actor ('Buyer:') and the outcome, then the mechanic and the revocation escape hatch. Every clause carries information; nothing is repeated from the schema or annotations.

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 output schema, the description usefully names setup_url, which is evidently a returned value the agent must act on. The absence of any statement about calling it twice (idempotentHint is false) or about what the mandate record contains leaves a modest gap, but the essential call-time picture is complete.

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 every parameter (including the required monthly_budget_minor, the per-order cap, currency, purpose, api_key) is already documented in the schema. The description reinforces the budget/cap concepts and the currencies' effect in prose but adds no format or constraint detail beyond what the schema states. Baseline 3 applies.

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 conveys a specific operation: letting a buyer's principal pre-authorize purchases by saving a card with Stripe and setting a budget and per-order cap. It also distinguishes itself from `buy` (where the mandate is then used) and `revoke_mandate` (which undoes it). It never states plainly 'this creates a spending mandate,' so the verb+resource pairing is inferred from the name plus narrative rather than declared outright.

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?

The triggering condition is clear: a buyer wants purchases to happen without a payment link, so the principal delegates spending instead. The revocation path is named explicitly ('Revocable any time with revoke_mandate'), giving an alternative for the opposite operation. It does not say whether this must precede `buy`, whether it fails when a mandate already exists, or what prerequisites (agent registration, API key) apply.

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