Skip to main content
Glama

create_pool

Creates a shared token-bucket quota pool for multiple agents to draw from within capacity, refill, burst, and per-agent limits, returning starting availability.

Instructions

Create a token-bucket quota pool shared by many agents. Costs 1 credit. Returns the pool with its starting availability.

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": {
      "name": "<name>",
      "capacity_units": "<capacity_units>",
      "refill_units_per_minute": "<refill_units_per_minute>",
      "per_agent_cap_units": "<per_agent_cap_units>",
      "burst_units": "<burst_units>"
    },
    "name": "create_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
burst_unitsYes
capacity_unitsYes
per_agent_cap_unitsYes
refill_units_per_minuteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the operation costs 1 credit and it returns the pool with starting availability. However, it omits whether the call is idempotent, what happens on name collisions, whether creation requires prior credit balance, and whether the pool is immediately active—significant gaps for a creation call with zero annotation coverage.

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?

Three short sentences, front-loaded with the purpose, then cost, then return value—no filler. It is slightly too terse for the amount of undocumented surface area, but as a writing sample it is well-structured.

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 five-parameter, all-required creation tool with no annotations and no output schema, the definition explains almost nothing about parameter meaning or failure behavior. The credit cost and return value are covered, but an agent still lacks enough to call this correctly without guessing at the parameters.

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% across five required parameters, so the schema adds no meaning at all. The description mentions 'token-bucket' and 'starting availability,' which loosely evokes capacity/refill/burst semantics, but it never maps those concepts to the actual parameters (capacity_units, refill_units_per_minute, per_agent_cap_units, burst_units) or explains units and constraints.

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 ('Create a token-bucket quota pool') plus a distinguishing property ('shared by many agents'), which separates it from per-agent tools like draw. It doesn't name any sibling explicitly, so the differentiation is inferred rather than stated.

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 phrase 'shared by many agents' implies a usage context, but there is no explicit when-to-use guidance, no prerequisites, and no mention of related tools such as get_pool, topup_pool, or list_pools that an agent would need to choose between.

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