Skip to main content
Glama

Set the targets of a pool

set_targets
DestructiveIdempotent

REPLACES the pool's targets with exactly this list (up to 25): send every target to keep. Each machine must be in the load balancer's private network (connect_vpc first). drain: true stops new connections to a target before maintenance. Scope: network.write.

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": {
      "lb": "<lb>",
      "pool": "<pool>",
      "targets": "<targets>"
    },
    "name": "set_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
lbYesLoad balancer id, as returned by list_load_balancers or create_load_balancer.
poolYesPool id, from get_load_balancer.
targetsYesThe pool's full list of targets, up to 25; [] empties the pool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / targets / description
      Added value: +"The pool's full list of targets, up to 25; [] empties the pool."
    • addedInput schema / properties / targets / items / properties / drain / description
      Added value: +"true stops sending new connections to this target; open ones finish. Default false."
    • addedInput schema / properties / targets / items / properties / weight / description
      Added value: +"Share of traffic relative to the other targets, 1 to 256. Default 1."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, but the description goes further by explaining exactly what is destroyed (any target omitted from the list) and the 25-target ceiling. It also discloses the auth scope (network.write) and the drain behavior's purpose (maintenance), which annotations cannot convey.

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?

Roughly three terse clauses with the most consequential fact (REPLACES) capitalized and front-loaded. No filler; each fragment (cap, prerequisite, drain, scope) carries a distinct operational fact.

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 destructive three-parameter mutation with no output schema, the definition covers the dangerous semantics, the prerequisite, the size limit, and the permission scope — everything needed to call it safely. Minor gaps remain around error behavior and whether ordering matters, but nothing that would cause a wrong invocation.

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 coverage is 100%, so lb, pool, targets, vm, port, drain and weight are all documented in structured fields; baseline is 3. The description adds only marginal param meaning — reinforcing that the targets array is the complete list and framing drain as a maintenance toggle — so it doesn't rise above baseline.

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?

Opens with an emphasized specific verb-plus-resource: "REPLACES the pool's targets with exactly this list." The replace-vs-append semantics immediately distinguish it from pool-management siblings like upsert_pool or delete_pool without needing to open any schema.

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

Usage Guidelines4/5

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

Gives the key usage rule ("send every target to keep") plus a hard prerequisite — "Each machine must be in the load balancer's private network (connect_vpc first)" — naming the sibling that satisfies it. It stops short of explicit when-not guidance, but the dominant failure mode (accidentally dropping targets) is pre-empted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.