Skip to main content
Glama

topup_pool

Add units to a shared quota pool, automatically capped at its capacity and free of billing credit charges. Use it to replenish a pool for agents drawing from its quota.

Instructions

Add units to a pool, clamped at capacity. Free — no billing credit is charged.

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": {
      "pool_id": "<pool_id>",
      "units": "<units>"
    },
    "name": "topup_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYes
pool_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose two valuable facts — that the addition is clamped at capacity and that no billing credit is charged — but says nothing about whether negative units are accepted, what happens if pool_id does not exist, or whether the call is idempotent. That leaves important mutation semantics undisclosed.

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?

Two short sentences, zero filler, with the action and its clamping rule front-loaded ahead of the cost note. Every clause carries information an agent needs.

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

Completeness3/5

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

For a simple two-parameter mutation with no output schema, the description covers purpose, cost, and the clamping rule, which is a reasonable minimum. It omits what the call returns (e.g., resulting balance) and failure behavior, which matters because no output schema or annotations fill that gap.

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%, so the description must compensate and only partly does: it clarifies that 'units' is an amount added and that the effective addition is capped at capacity. It never explains pool_id or constrains units to non-negative values, leaving half the parameters undocumented in both places.

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 ('Add units to a pool') plus the key constraint that the addition is clamped at capacity, which clearly separates it from create_pool or draw. It never explicitly names a sibling to contrast with, so it stops short of a 5.

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?

The description implies when the tool applies but gives no explicit when-to-use guidance, no prerequisites, and no contrast with alternatives such as draw (consuming units) or create_pool. The agent must infer that this is the replenishment path.

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