Skip to main content
Glama

Create or update a pool

upsert_pool

Without pool: creates one (name required, up to 10). With pool: changes only the fields given. Deleting a pool also removes its targets and the rules leading to it. 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>"
    },
    "name": "upsert_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
lbYesLoad balancer id, as returned by list_load_balancers or create_load_balancer.
nameNoLetters, digits, spaces, . _ -; unique in the load balancer.
poolNoPool id, from get_load_balancer.
protocolNohttp pools serve http/https listeners, tcp pools tcp listeners. Default http; cannot change once in use.
algorithmNoroundrobin (default) takes targets in turn, by weight; leastconn picks the one with the fewest open connections, for long-lived connections.
send_proxyNotcp pools only: PROXY protocol v2 to the targets.
health_pathNoe.g. /health
health_typeNohttp (http pools only): GET health_path, 2xx or 3xx is healthy. Default tcp.
health_intervalNoSeconds between checks, default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / algorithm / description
      Added value: +"roundrobin (default) takes targets in turn, by weight; leastconn picks the one with the fewest open connections, for long-lived connections."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnly=false, destructive=false, openWorld=true; the description adds genuinely useful context beyond them by stating the "network.write" scope and warning that deleting a pool also removes its targets and inbound rules. That cascade note sits a little awkwardly against destructiveHint=false and refers to a different operation than this upsert, so the behavioral picture is helpful but not fully coherent.

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?

Three short clauses, front-loaded with the create/update decision, then the cascade consequence, then the permission scope. No filler sentences.

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 9-parameter upsert with full schema coverage, the description covers mode selection, the creation precondition, cascade side effects, and permission scope. It leaves the pool-count limit ambiguous and says nothing about what the call returns, which matters somewhat since no output schema exists.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning the schema lacks: `name` is effectively required on creation even though only `lb` appears in the schema's required list, and updates are explicitly partial ("changes only the fields given"). It does not resolve the ambiguous "up to 10" limit.

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 the verb plus resource explicitly and splits behavior by mode: no `pool` creates, with `pool` updates only the supplied fields. Distinct from siblings like delete_pool or upsert_listener. The phrase "up to 10" is undefined (10 pools per load balancer?), which keeps it from a 5.

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 a clear rule for choosing create-vs-update behavior based on whether `pool` is supplied, plus the name-required precondition for creation. It does not name a sibling alternative (e.g., delete_pool) for removal, but the mode split covers the main decision an agent faces.

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.