Skip to main content
Glama

Set the daily agent spending cap

autoshort_set_limits
DestructiveIdempotent

Set a daily agent spending cap in credits. Lowering it applies immediately; raising it returns an approval link the signed-in account owner must open to approve.

Instructions

Set this key's daily agent spending cap in credits. Lowering (or keeping) it applies immediately. Raising it returns approvalUrl: the account owner must open it while signed in and approve — an agent cannot raise its own cap. Free.

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": {
      "dailyCreditCap": "<dailyCreditCap>"
    },
    "name": "autoshort_set_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyCreditCapYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which already flag destructiveHint=true, idempotentHint=true, readOnlyHint=false), the description discloses the critical asymmetric behavior: decreases take effect at once, increases are gated behind an owner approval URL that an agent cannot satisfy itself. It also notes the call is free, which annotations do not cover.

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 and then the two behavioral branches. No filler, and the most surprising fact (the approval flow) is placed where it will be read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation with no output schema, the description covers what an agent needs: what the parameter means, what happens on decrease versus increase, what is returned on the increase path, and that there is no cost.

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% for the single required parameter, so the description must compensate. It does so by establishing the unit ('in credits') and the scope ('daily'), though it leaves the day boundary and how the cap interacts with the credit balance unspecified.

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+resource+scope: 'Set this key's daily agent spending cap in credits.' That is unambiguous and clearly distinct from reading limits (autoshort_get_limits) or buying credits (autoshort_buy_credits), though it never names an alternative explicitly.

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 gives practical context for the two cases that matter: lowering or keeping the cap applies immediately, while raising it requires the owner to approve via a returned approvalUrl. It does not explicitly point to a sibling for reading the current cap, so guidance is strong but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.