Skip to main content
Glama

Load balancer statistics

get_load_balancer_metrics
Read-only

Requests by response class, connections, bytes in/out and peak sessions over 1h (1-minute buckets), 24h (15 minutes) or 7d (1 hour), plus totals. Scope: vms.read.

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": "get_load_balancer_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
lbYesLoad balancer id, as returned by list_load_balancers or create_load_balancer.
rangeNoPeriod covered. Default 1h.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / range / description
      Added value: +"Period covered. Default 1h."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the permission scope (vms.read) and the bucket granularity per range, which is genuine extra context, but says nothing about pagination, retention limits, or empty-result behavior.

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?

A single dense sentence that front-loads the returned metrics, then the time ranges with their granularity, then the permission scope. No filler and no repetition of the schema.

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?

With no output schema, the description carries the burden of describing return values, and it does so by listing the metric families and noting totals. It is nearly complete for a two-parameter read tool; only aggregation or empty-window behavior is unaddressed.

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, and the description earns above that by mapping each range value to its bucket size (1h=1-minute, 24h=15-minute, 7d=1-hour), which the enum alone does not convey. The lb parameter's meaning is left entirely to the schema.

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 names the specific resource (load balancer) and enumerates the exact metrics returned: requests by response class, connections, bytes in/out, peak sessions, plus totals. This clearly separates it from get_load_balancer, which returns the object itself, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the metric content and the 'Scope: vms.read' note; there is no explicit statement of when to call this versus get_load_balancer or get_vm_metrics, nor any exclusions. An agent can infer it is a monitoring call, but must reason about alternatives itself.

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.