Skip to main content
Glama

delete_pool

Deletes a specified quota pool and all its draw history; no billing credits are charged or refunded. Use to remove obsolete shared quota pools without changing billing.

Instructions

Delete a pool and its draws. No billing credit is charged or refunded.

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>"
    },
    "name": "delete_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pool_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 does disclose two useful traits: the delete cascades to draws, and no billing credit is charged or refunded. It omits irreversibility, required permissions, and what happens when the pool_id does not exist, which matter for a destructive operation.

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?

Two short sentences with no waste, and the destructive scope is front-loaded ahead of the billing footnote. Efficient and easy to scan.

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

Completeness4/5

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

For a single-parameter destructive tool with no annotations and no output schema, the definition covers the two things an agent could not infer: the cascade to draws and the absence of billing effects. Remaining gaps (irreversibility, missing-id behavior) are modest given the tool's simplicity.

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?

One parameter at 0% schema description coverage, so the description must compensate. It implicitly identifies pool_id as the pool whose draws are also removed, which clarifies what the entity is, but adds nothing about identifier format, source, or error behavior for an invalid id.

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 ('Delete a pool') and adds scope the name alone doesn't convey: its draws are deleted too. It is distinguishable from create_pool/get_pool/list_pools by the verb, though it never names a sibling or contrasts behavior explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the destructive verb; there is no when-to-use versus when-to-avoid guidance, no prerequisite that the pool be empty or exist, and no pointer to an alternative such as draining draws first. The billing sentence hints at a use case (removing pools without credit impact) but does not state it as guidance.

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