Skip to main content
Glama

Spending controls

set_spending_controls
DestructiveIdempotent

Cap per-delivery and rolling 24-hour spend in workspace currency minor units. Zero blocks, null clears. Defaults to original workspace.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_spending_controls"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idNo
daily_cap_centsNo
spending_cap_per_delivery_centsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already flag this as a non-read-only, destructive, idempotent mutation, and the description adds genuinely useful semantics beyond that: amounts are in minor units in workspace currency, a value of zero blocks spending entirely, and null clears the cap. It stops short of saying whether the change applies to in-flight or already-funded deliveries and what authorization is required.

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 tight sentences, front-loaded with the main effect before the edge-case rules and the default. The clause 'Zero blocks, null clears' is very terse and could be momentarily misread as a noun phrase, but overall every sentence earns its place.

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 destructive mutation with zero schema documentation and no output schema, the description covers the essential value semantics but omits consequences (does zeroing a cap halt scheduled deliveries or only future ones?), required permissions, and whether omitted fields are left untouched. It is adequate to call safely, but a cautious agent would still lack key context.

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 0%, so the description must carry the burden and largely does: it maps the two cap parameters to per-delivery and rolling 24-hour semantics, explains the units (minor units, workspace currency), defines the sentinel values (zero blocks, null clears), and says workspace_id defaults to the original workspace. The only gap is that the sentinel rules are not tied explicitly to each named field.

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 action and scope: cap per-delivery spend and rolling 24-hour spend in workspace currency minor units. There is no obvious sibling for billing controls in the listed set, so no sibling differentiation is attempted, but the resource ('spend' caps) and the two cap dimensions are unambiguous.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g., required permission or plan), and no statement of what this affects relative to delivery/booking tools. 'Defaults to original workspace' tells the agent how workspace_id resolves, but not when to call this tool versus anything else.

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.