Skip to main content
Glama
Sign In
@argosvix/mcp-server

@argosvix/mcp-server

by argosvix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_budget_gate

Update a runtime budget gate by modifying its monthly limit, enforcement mode, or enabled status. Use to adjust spending controls dynamically.

Instructions

Update a runtime budget gate (Pro+ only). Partially updates any of monthlyLimitUsd / enforceMode / enabled. Example phrasing: "raise the limit to $100" / "disable the gate temporarily" / "switch to fail_closed"

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": {
      "gateId": "<gateId>"
    },
    "name": "update_budget_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateIdYesTarget gate id (from get_budget_gate, starts with bg_)
enabledNoWhether the gate is enabled
enforceModeNoBehavior when the backend is unreachable
monthlyLimitUsdNoNew monthly limit in USD (0.01 - 1000000, $0.01 increments)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.30.0-alpha.14

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states 'Partially updates' which implies it is not destructive, but does not disclose any other behavioral traits such as auth requirements (Pro+ only is a plan restriction, not direct auth), rate limits, or idempotency. Somewhat adequate but could be more transparent.

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?

The description is concise: two sentences plus an example list. Every sentence adds value, and the information is front-loaded. No unnecessary words.

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?

Given the tool's complexity (4 parameters, 1 required, no output schema), the description adequately covers what the tool does and how to use it with concrete examples. It is complete for an agent to understand and invoke the tool correctly.

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 coverage is 100% with each parameter having a description. The tool description adds value by providing usage examples mapping to parameters (e.g., 'raise the limit to $100' to monthlyLimitUsd). However, it does not substantially enhance understanding beyond the schema, so baseline 3 is appropriate.

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?

The description clearly identifies the action 'Update' and the resource 'runtime budget gate'. It mentions 'Partially updates any of monthlyLimitUsd / enforceMode / enabled', which distinguishes it from sibling tools like create, delete, or get budget gates.

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?

Examples are provided ('raise the limit to $100', 'disable the gate temporarily', 'switch to fail_closed') that illustrate typical use cases. However, there is no explicit guidance on when not to use this tool or alternatives, such as when to use create_budget_gate instead.

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

Deploy Server

Other Tools