Skip to main content
Glama

Agent Budget Guard

wever_agent-budget-guard

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Evaluates caller-supplied policy, usage and request values only. No live allowance or balance is read, no destination is contacted, no budget or run is reserved, and no permission or execution authority is granted. Operating boundary: Direct access uses x402 Base USDC settlement or the verified-wallet free tier. Evaluates caller-supplied policy, usage and request values only. No live allowance or balance is read, no destination is contacted, no budget or run is reserved, and no permission or execution authority is granted. The API access fee is separate from any inspected payment or recorded invoice amount. POST /api/agent-budget-guard. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. This current money service follows its published inspection, policy evaluation or private invoice contract. Payment is an API access fee and grants no spending authority.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
usageYes
policyYes
requestYes
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • removedInput schema / description
      Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."
    • removedInput schema / maxProperties
      Removed value: -64
    • removedInput schema / minProperties
      Removed value: -1
    • addedInput schema / properties / agent_id
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +  "type": "string"
      +}
    • addedInput schema / properties / mode / const
      Added value: +"evaluate_action"
    • removedInput schema / properties / mode / maxLength
      Removed value: -128
    • removedInput schema / properties / mode / minLength
      Removed value: -1
    • removedInput schema / properties / mode / type
      Removed value: -"string"
    • addedInput schema / properties / policy
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "agent_id": {
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +      "type": "string"
      +    },
      +    "allowed_callback_origins": {
      +      "items": {
      +        "description": "Canonical HTTPS origin only, with no path, trailing slash, credentials, query or fragment. Matching uses the parsed request URL origin; no destination is contacted.",
      +        "maxLength": 256,
      +        "minLength": 9,
      +        "type": "string"
      +      },
      +      "maxItems": 16,
      +      "minItems": 0,
      +      "type": "array",
      +      "uniqueItems": true
      +    },
      +    "allowed_rails": {
      +      "items": {
      +        "maxLength": 64,
      +        "minLength": 1,
      +        "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +        "type": "string"
      +      },
      +      "maxItems": 16,
      +      "minItems": 0,
      +      "type": "array",
      +      "uniqueItems": true
      +    },
      +    "budget_minor": {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "callback_required": {
      +      "type": "boolean"
      +    },
      +    "currency": {
      +      "const": "USD"
      +    },
      +    "expires_at": {
      +      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z(?![\\s\\S])",
      +      "type": "string"
      +    },
      +    "max_action_fee_minor": {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "max_runs": {
      +      "maximum": 1000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "not_before": {
      +      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z(?![\\s\\S])",
      +      "type": "string"
      +    },
      +    "policy_id": {
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "policy_id",
      +    "agent_id",
      +    "currency",
      +    "budget_minor",
      +    "max_action_fee_minor",
      +    "max_runs",
      +    "allowed_rails",
      +    "allowed_callback_origins",
      +    "callback_required",
      +    "not_before",
      +    "expires_at"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "callback_url": {
      +      "anyOf": [
      +        {
      +          "description": "ASCII HTTPS URL without credentials, control characters, backslashes or fragment. Its normalized origin is compared exactly with allowed_callback_origins. No request is sent.",
      +          "maxLength": 2048,
      +          "minLength": 9,
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "fee_minor": {
      +      "description": "Total fee for this action request in USD cents, including all requested runs. It is not multiplied by run_count.",
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "rail_key": {
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "pattern": "^[A-Za-z0-9][A-Za-z0-9._:-]{0,63}(?![\\s\\S])",
      +      "type": "string"
      +    },
      +    "run_count": {
      +      "maximum": 1000000,
      +      "minimum": 1,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "rail_key",
      +    "fee_minor",
      +    "run_count",
      +    "callback_url"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / usage
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "as_of": {
      +      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}Z(?![\\s\\S])",
      +      "type": "string"
      +    },
      +    "spent_minor": {
      +      "maximum": 1000000000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "used_runs": {
      +      "maximum": 1000000,
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "spent_minor",
      +    "used_runs",
      +    "as_of"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / required
      Added value: +[
      +  "mode",
      +  "agent_id",
      +  "policy",
      +  "usage",
      +  "request"
      +]
  2. First observed

TDQS

C2.7/5.0
Behavior4/5

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

With annotations present (readOnlyHint=false, openWorldHint=true), the description still adds real context: no live allowance or balance is read, no destination is contacted, no budget or run is reserved, and no authority is conferred. The pricing model and free-call quota are also disclosed. The negative framing is dense but genuinely informative beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text repeats itself almost verbatim – 'Evaluates caller-supplied policy, usage and request values only. No live allowance or balance is read, no destination is contacted...' appears twice, and the 'grants no authority' point is restated three times. It is bloated rather than front-loaded.

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

Completeness2/5

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

For a complex, nested-schema tool with no output schema and 0% parameter documentation, the description explains the authority/safety boundary well but says nothing about inputs or what the evaluation returns. An agent could not reliably construct a valid call from this alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and five required parameters (including nested policy/usage/request objects with many sub-fields) are undocumented. The description only names 'policy, usage and request' at a high level and gives no field-level meaning, formats, or constraints for any of them.

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

Purpose3/5

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

The description does state a specific function – 'Evaluates caller-supplied policy, usage and request values only' – but it is buried under repetitive negation clauses. It never clearly frames itself alongside siblings like wever_payment-authority-inspector or wever_agent-allowance-console, so an agent must infer that this is a pre-flight budget/policy check.

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?

Pricing and free-tier mechanics are given, but there is no explicit guidance on when to call this versus the many sibling rails. Statements that 'existing product credentials, signed mandates, and single-use action grants remain required' hint at prerequisites but never translate into a use/do-not-use rule.

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.