Skip to main content
Glama

Get machine metrics

get_vm_metrics
Read-only

CPU, memory, disk and network as measured from outside the machine. 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": {
      "vm": "<vm>"
    },
    "name": "get_vm_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmYesMachine id, as returned by list_vms or create_vm.
timeframeNoPeriod covered, ending now. Default hour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / timeframe / description
      Added value: +"Period covered, ending now. Default hour."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two genuinely new facts not in annotations: the measurement is external to the machine, and the call requires the vms.read scope, which helps an agent reason about permission failures. It stops short of disclosure about granularity, sampling interval, or freshness of the returned data.

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?

Two terse sentences that lead with the payload contents and follow with the scope constraint; no filler or restated title. Extreme brevity is the only knock, as it trades completeness for compactness.

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

Completeness3/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 is the only place return shape could be conveyed, yet it says nothing about units, aggregation, per-metric structure, or how timeframe affects granularity. Inputs and permissions are adequately covered, so it is viable but leaves a real gap for a metrics-reading tool.

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 description coverage is 100%, with the vm parameter pointing at list_vms/create_vm and the timeframe enum documenting its values and default. The description contributes nothing additional about either parameter, so the baseline 3 applies.

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?

Names the specific resource measured (CPU, memory, disk, network) and distinguishes the data source as 'measured from outside the machine', which separates it from an in-guest agent reading. It doesn't explicitly contrast with get_vm or get_vm_network, but the metric-set enumeration is concrete enough to identify the tool.

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

Usage Guidelines2/5

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

The only guidance is 'Scope: vms.read', which is an authorization requirement rather than a when-to-use rule. Nothing tells the agent when to pick this over get_vm, get_vm_network, or the sibling get_database_metrics/get_load_balancer_metrics, nor any prerequisite like the VM needing to exist or be running.

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.