Skip to main content
Glama

Read how much of its size a server used with players online

getServerUsage
Read-onlyIdempotent

Returns the time the server spent with at least one player online in its latest unbroken run on its current size (its last 7 days with players, or more days back until they hold 8 hours), histograms of CPU, tick load, GC pause share, memory peak, the JVM's live set and memory outside its heap over that time, and suggestion: the smaller, cheaper size that would carry the same play, or null when the current size is needed or the evidence is too thin: at least 3 hours of play with a clear margin, or 8 hours otherwise. Use suggestion to answer whether the server can run on a smaller size; changing size is updateServer with the target size and applies on the next start.

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": {
      "path": "<path>"
    },
    "name": "getServerUsage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it defines the measurement window (latest unbroken run, last 7 days with players, or further back until 8 hours accumulate) and the null conditions for suggestion with explicit evidence thresholds (3 hours with clear margin, or 8 hours otherwise). An agent knows exactly how to interpret a null suggestion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

All content has value, but the first sentence is an extremely long run-on packing the window definition, six histogram families, and suggestion semantics into one clause chain. It is not front-loaded on the primary outcome (can this server be smaller?) and would read far better split into structured 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?

With no output schema, the description carries the return-value burden and does so thoroughly: the time figure, each histogram, and the suggestion field with its null conditions are all described. The remaining shortfall is the unexplained `path`/serverId parameter, which the description never touches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% at the top level: the single parameter is a nested `path` object whose purpose is never explained in the description, and the description never mentions serverId or where to obtain it. The nested schema does document serverId ('the id field from listServers'), which keeps this from being a total gap, but the object wrapper remains unexplained and the description contributes nothing.

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 a specific read operation and enumerates exactly what is returned: time with players online, CPU/tick/GC/memory histograms, and a size suggestion. It explicitly contrasts with updateServer for acting on the suggestion, though it never distinguishes itself from the close sibling getServerMetrics.

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 concrete downstream guidance: 'Use suggestion to answer whether the server can run on a smaller size; changing size is updateServer with the target size and applies on the next start.' That names the alternative and the effect of taking it. It lacks any when-not-to-use guidance, e.g. versus getServerMetrics for raw metrics.

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.

Resources