Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Proxy Pool Clear

proxy_pool_clear

Clears all proxy pool entries, including stickies, while preserving the rotation strategy.

Instructions

Drop ALL entries. Stickies cleared. Rotation strategy preserved.

Ex: proxy_pool_clear() → {"cleared":12}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxy_pool_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the safety burden and does disclose key effects: all entries are dropped, stickies are cleared, and the rotation strategy is preserved. The example return value adds useful context, though irreversibility and permission requirements are not explicitly stated.

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?

The description is front-loaded and waste-free: it states the destructive effect first, then preserved state, then a compact example. Every sentence adds useful information for a zero-parameter tool.

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 zero-parameter destructive tool with an output schema, the description covers the essential effect and the preserved rotation strategy. It could be stronger by explicitly warning about irreversibility or naming the alternative for selective removal, but the core behavior is clear.

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

Parameters4/5

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

The tool has zero parameters, so the schema baseline is 4 and there are no parameter semantics to miss. The description appropriately does not waste space documenting nonexistent inputs.

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

Purpose5/5

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

The description uses the specific verb 'Drop' with the scope 'ALL entries', making clear this is a full clear rather than a targeted removal. It distinguishes itself from siblings like proxy_pool_remove by emphasizing ALL, and the example reinforces the effect.

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 states what the tool does but gives no explicit guidance on when to use it instead of proxy_pool_remove, proxy_pool_load, or other pool-management siblings. There is no mention of prerequisites, confirmation, or when-not-to-use for this destructive operation.

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

Deploy Server

Other Tools