Skip to main content
Glama

Set daily cap

set_daily_cap
Idempotent

Sets your own daily spend cap in Wave credits; paid calls past it fail until the next UTC day. Returns the new cap. Free. Needs sign-in (auth_challenge then auth_verify).

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": {
      "daily_cap": "<daily_cap>"
    },
    "name": "set_daily_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
daily_capYesCredits per UTC day, 0 up to the maximum

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / daily_cap / description
      Added value: +"Credits per UTC day, 0 up to the maximum"
    • addedInput schema / properties / daily_cap / minimum
      Added value: +0
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive mutation; the description adds genuine behavioral context on top: over-cap paid calls fail until the next UTC day, the call itself costs nothing, and it returns the new cap. It stops short of explaining what setting the cap to 0 means (the schema permits 0 but neither field defines it as blocking all spend).

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?

Four short clauses, zero filler: action, consequence, return value, cost, and auth requirement, with the action front-loaded. Nothing could be removed without losing information.

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 one-parameter mutation with no output schema, the description covers action, side effect, return value, cost, and the required auth sequence, which is everything an agent needs to call it 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 description coverage is 100% and the single parameter already documents credits per UTC day with min/max bounds. The description reinforces the UTC-day unit and credit currency but adds no format or edge-case meaning beyond the schema, so the baseline of 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?

States a specific verb and resource ('Sets your own daily spend cap in Wave credits') and narrows scope with 'your own', so it is not confused with any balance or credit-reading sibling. No sibling tool performs a comparable action, so there is no explicit differentiation to make, which keeps it at 4 rather than 5.

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 a concrete precondition and routing: 'Needs sign-in (auth_challenge then auth_verify)', naming two siblings in the correct order. It also clarifies the call is free, which matters given the credit-based ecosystem, but does not state when an agent should change versus leave a cap alone.

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