Skip to main content
Glama

Set the monthly X spending limit

set_x_budget
DestructiveIdempotent

X bills Shager for every read, reply and DM. This sets the most, in US dollars, that this workspace may use on X per calendar month (UTC) for comments and auto-replies; 0 turns X comments and auto-replies off. Default 5. Lowering it takes effect at once. Raising it spends the customer's money, so a workspace manager approves it in Shager first: the first call answers needs_confirmation with confirm_url; after they approve, make the same call again. (Not available in an unclaimed sandbox.)

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": {
      "workspace_id": "<workspace_id>",
      "monthly_limit_usd": "<monthly_limit_usd>"
    },
    "name": "set_x_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesWorkspace id from list_workspaces
monthly_limit_usdYesUS dollars per month, e.g. 5
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmation_token
      Added value: +{
      +  "description": "The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses real consequences: the customer is billed per read/reply/DM, raising the limit spends the customer's money and therefore requires workspace-manager approval via needs_confirmation plus confirm_url, and lowering takes effect immediately. The retry semantics ('make the same call again') and sandbox restriction are exactly the operational facts an agent needs.

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 core action and cost model, then the approval flow, then the sandbox caveat in parentheses. Dense but every clause carries actionable information; a slightly tighter split of the billing sentence would make it perfect.

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?

With no output schema, the description still explains the two-step return path (needs_confirmation with confirm_url, then resubmit) and the effective-timing rules. Nothing an agent needs to invoke or recover from this mutation is missing.

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 100%, so the baseline is 3; the description goes further by explaining that 0 turns the feature off, that the value is USD per calendar month (UTC), and that confirmation_token comes from the needs_confirmation response. It adds genuine meaning, though it does not restate the 0-1000 bounds already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('sets the most, in US dollars, that this workspace may use on X per calendar month') and names the scope (comments and auto-replies). It is clearly distinguishable from neighbouring set_* tools such as set_audience or set_channel_status, which govern different resources.

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 strong when-to-use context: 0 disables X comments and auto-replies, the default is 5, lowering applies at once, and the tool is unavailable in an unclaimed sandbox. It does not name an explicit alternative tool for changing spend another way, so it falls just short of a full 5.

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