Skip to main content
Glama

Proxy Pool List

proxy_pool_list

Lists all proxy pool entries with credentials redacted by default, showing rotation strategy and entry details. Set redact to false to include credentials.

Instructions

List all entries (creds redacted by default). Columnar.

Ex: proxy_pool_list() → {"rotation":"round_robin","entries":[...]}

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
redactNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the disclosure burden and does add useful behavior: credentials are redacted by default, output is columnar, and an example response is shown. However, it does not explicitly state read-only safety, permissions requirements, pagination behavior, or what changes when redaction is disabled.

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 tightly front-loaded: purpose first, then redaction behavior, output format, and a compact example. Every fragment contributes useful information with no waste.

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 simple one-parameter list tool with an output schema, the description is mostly complete: it names the operation, notes redaction behavior, describes output style, and shows an example response. The only notable gap is fuller explanation of the redact parameter and its security implications.

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 0%, so the description must compensate for the undocumented redact parameter. It does partially compensate by stating "creds redacted by default," which explains the default value and effect, but it does not explain the consequences of setting redact to false.

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?

The description gives a specific verb and resource: "List all entries" in the proxy pool, with additional context about redaction and output shape. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as proxy_pool_export or proxy_pool_health_check.

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 provides no explicit when-to-use guidance, prerequisites, or comparison with sibling tools like proxy_pool_export or proxy_pool_health_check. Listing is implied by the verb, but an agent must infer the appropriate context from the tool name alone.

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