Skip to main content
Glama

create_spending_mandate

Account controller creates a restricted buyer token. You must have the owner's authorization to allocate these limits; do not mint one to escape a budget. Token returned once. Limits immutable, gross authorizations include refunded jobs. UTC daily cap and lifetime cap enforced atomically. Root identity is not verified legal ownership.

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": {
      "max_per_run": "<max_per_run>",
      "max_per_day": "<max_per_day>",
      "max_total": "<max_total>",
      "expires_at": "<expires_at>"
    },
    "name": "create_spending_mandate"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_totalYes
expires_atYesEpoch milliseconds, within next 30 days
seller_idsNo
max_per_dayYes
max_per_runYes
capability_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world, non-destructive, so the bar is lower; the description still adds real traits beyond that: limits are immutable, gross authorizations include refunded jobs, UTC daily and lifetime caps are enforced atomically, the authorization caveat that root identity is not verified legal ownership. What it omits is failure behavior (what happens on cap breach, denial, or expired scope).

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?

Front-loaded with the action and the authorization constraint, and every sentence carries information. The telegraphic fragment style ('Token returned once. Limits immutable...') is efficient but slightly clipped, requiring the reader to reconstruct subject and object.

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?

No output schema exists, so the description must convey the return: it says the token is returned once, which is useful, but not what else accompanies it. For a 6-parameter mutation that mints a credential, the scope parameters (seller_ids, capability_ids) and error/denial behavior remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 17% across 6 parameters, so the description must carry the load. It clarifies that caps are gross and UTC-based and enforced atomically, but says nothing about seller_ids or capability_ids, which define the mandate's scope, nor about max_per_run versus max_per_day versus max_total distinctions. Only the expires_at parameter is documented elsewhere (in the 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?

States a specific verb and resource: 'creates a restricted buyer token' tied to spending limits. The only friction is the naming mismatch between the tool name (spending mandate) and the description (buyer token), but an agent can still tell this apart from current_spending_mandate/revoke_spending_mandate as the creation entry point.

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?

Gives a clear precondition ('must have the owner's authorization to allocate these limits') and an explicit exclusion ('do not mint one to escape a budget'). It does not name sibling alternatives such as current_spending_mandate or revoke_spending_mandate, so routing to the right tool is left partly to inference.

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