Skip to main content
Glama

Create a Machine

varity_machines_create

Create a Varity CPU or GPU virtual machine developers can SSH into using their public key; supply profile and OS image, and delete it to stop hourly billing.

Instructions

Create a Varity CPU or GPU virtual machine the developer can SSH into. Requires the developer's own SSH PUBLIC key (e.g. the contents of ~/.ssh/id_ed25519.pub); never pass a private key. Get profile_id and os_image from varity_machines_list with include_profiles (and gpu: true for a GPU VM, then pass gpu: true here too). The machine bills hourly until varity_machines_delete.

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>",
      "profile_id": "<profile_id>",
      "os_image": "<os_image>",
      "ssh_public_key": "<ssh_public_key>"
    },
    "name": "varity_machines_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpuNoCreate a GPU virtual machine from a GPU VM profile.
nameYesLowercase machine name, e.g. 'dev-box'.
os_imageYesOS image id offered by that profile (os-...).
profile_idYesMachine profile id (mp-...).
ssh_public_keyYesThe developer's SSH public key, e.g. 'ssh-ed25519 AAAA... user@host'.
idempotency_keyNoReuse the same key to retry a create without creating a second machine.
additional_storage_gbNoExtra disk in GB (CPU machines only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false. The description adds genuinely new behavior: hourly billing until delete and the public-key-only security constraint. It still omits what a successful create returns (machine id/handle) and does not mention the idempotency_key parameter's retry semantics, which is the main behavioral gap.

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 sentences, front-loaded with the action and its SSH requirement, then prerequisites, then cost/cleanup. Parenthetical examples are short and functional; no sentence is expendable.

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?

For a seven-parameter creation tool with no output schema, the definition covers prerequisites, key safety, GPU selection, and billing consequences, which is nearly everything an agent needs. The remaining gap is the return value and the idempotency_key retry behavior, which are left undocumented.

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 baseline is 3; the description earns above that by specifying where profile_id and os_image come from and by emphasizing the public-key format and the public-vs-private distinction. The gpu flag's coupling with the profile choice is also clarified. It does not cover additional_storage_gb or idempotency_key, leaving those to the schema.

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 description opens with a specific verb and resource ('Create a Varity CPU or GPU virtual machine the developer can SSH into'), naming both variants and the access method. It separates this tool from varity_machines_list (profile lookup) and varity_machines_delete (billing stop) without ambiguity.

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

Usage Guidelines5/5

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

It states explicit prerequisites and ordering: fetch profile_id and os_image from varity_machines_list with include_profiles, set gpu: true in both calls for a GPU VM, and never pass a private key. It also names the lifecycle terminus, varity_machines_delete, so the agent knows how creation is undone.

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