Skip to main content
Glama

get_vm_usage

Estimate per-VM costs across all hypervisors from allocated vCPU, RAM, and disk, returning hourly and monthly figures sorted by expense.

Instructions

Get VM cost attribution across all hypervisors.

Returns per-VM cost estimate based on allocated vCPU, RAM, and disk. Includes hourly and monthly costs, sorted by most expensive first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vm_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavior beyond the name — the cost basis (allocated vCPU, RAM, disk), granularity (hourly and monthly), and ordering (most expensive first) — but it omits whether it is a pure read, whether unallocated or powered-off VMs are excluded, and whether results can be truncated.

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 lines, front-loaded with the resource and scope, then output basis, then result shape and ordering. Every sentence adds new information and none repeats the name or 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 parameters, no annotations, and no output schema, the description is the only documentation and it covers purpose, cost basis, time granularity, and sort order — enough to call and interpret it. It falls short only on data provenance (live usage vs. configured allocation) and result limits.

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?

The tool takes zero parameters, which is the baseline-4 case: there is nothing to document, and the description correctly signals a no-argument call. No meaning is lost.

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 verb and resource ('Get VM cost attribution') plus explicit scope ('across all hypervisors'), and the second sentence clarifies the unit of output (per-VM cost estimate). It does not name a distinguishing sibling such as get_cost_estimate or get_chargeback, so the agent must infer the boundary, which keeps it below 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 Guidelines3/5

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

Usage is only implied: the scope 'across all hypervisors' tells the agent this is a fleet-wide cost report rather than a single-VM lookup. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the cost-related siblings, so the agent has to infer routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools