Skip to main content
Glama

Create a load balancer

create_load_balancer
Idempotent

Orders a load balancer in a private network, billed by the hour from now (the account needs 24 hours of credit), or by the month (7.30 CAD) or the year (73 CAD) with billing. A monthly or yearly period comes out of credit if it covers it; otherwise billing.pending_invoice holds the invoice to pay and it stays hourly until then. Ready within minutes (status pending → active); pools and listeners can be added meanwhile. Retrying the same call is safe. Scope: vms.create.

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": {
      "name": "<name>",
      "vpc": "<vpc>"
    },
    "name": "create_load_balancer"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcYesPrivate network whose machines will be the targets (list_vpcs).
nameYesDisplay name of the load balancer, 1 to 64 characters.
billingNohourly (default), monthly (the price of 730 hours, paid in advance) or yearly (ten months). Ask the user; monthly or yearly needs credit or an invoice paid by the user.
idempotency_keyNoYour own unique value per order. By default one is derived from the call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Display name of the load balancer, 1 to 64 characters."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it as a non-destructive, idempotent, open-world write; the description goes well beyond that by explaining hourly billing starts now, that monthly/yearly draws from credit or lands in billing.pending_invoice and stays hourly until paid, and that the resource moves pending → active within minutes. That is exactly the kind of post-call state behavior an agent cannot infer from structured fields.

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?

What the tool does is front-loaded in the first clause, and every sentence carries information about billing, readiness, or safety. It is dense with parentheticals and long compound sentences, which costs some scannability but wastes little.

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

Completeness5/5

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

With no output schema, the description compensates by describing the resulting status transition (pending → active, ready within minutes) and the billing.pending_invoice field an agent will encounter. Combined with the prerequisite credit requirement, nothing essential for a correct call is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the billing interplay (credit coverage vs pending invoice, and the fallback to hourly) that the enum alone does not convey. It also reinforces idempotency_key semantics by stating retries are safe, which exceeds the schema's 'one is derived from the call'.

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 opening sentence names a specific verb and resource ('Orders a load balancer') plus its scope ('in a private network'), which distinguishes it immediately from the create_* VM/VPC/database siblings. An agent knows exactly what object is produced without opening the 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?

It gives real decision context: the account needs 24 hours of credit, the caller should ask the user about hourly vs monthly vs yearly, and the scope 'vms.create' signals permission prerequisites. It also hints that pools/listeners are added separately ('can be added meanwhile'), but never names the alternative billing-check or status-check tools, so routing guidance stops short of explicit alternatives.

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.