Skip to main content
Glama

Set spend limit

set_spend_limit
Destructive

Set or remove the monthly spend cap and its alert thresholds. Live sends over the cap are refused.

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_spend_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_thresholdsNoPercentages of the limit to alert at, up to 5, like [50, 80, 100]
monthly_limit_usdNonull removes the cap

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / alert_thresholds / description
      Added value: +"Percentages of the limit to alert at, up to 5, like [50, 80, 100]"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds a genuinely useful consequence: live sends over the cap are refused. It does not explain what makes the call destructive (are existing thresholds replaced wholesale?) or why it is non-idempotent, so the annotation semantics remain unexplained.

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 short sentences with zero filler, and the enforcement clause is placed after the action statement so the core capability lands first.

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?

For a two-optional-parameter mutation with no output schema, the definition covers action and enforcement effect, which is close to sufficient. Missing are the permission requirement, the replace-vs-merge behavior of alert_thresholds, and a pointer to get_spend_limit for read-back.

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% — both parameters document themselves, including that null removes the cap. The description's 'set or remove' framing echoes that without adding format, range, or interaction detail (e.g., whether thresholds are merged or replaced). 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 names a specific verb+resource pair — set or remove the monthly spend cap and its alert thresholds — so an agent knows exactly what is being configured. It does not, however, distinguish itself from the sibling get_spend_limit, which is the read counterpart an agent may need first.

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?

There is no statement of when to call this versus get_spend_limit, no mention of prerequisites (e.g., billing/owner permissions), and no guidance on whether to read the current limit before overwriting it. Usage is only implied by the verb.

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.