Skip to main content
Glama

Mount ISO on VPS

vps_mount_iso
Idempotent

Mount or unmount an ISO image on a VPS. Pass an ISO identifier to mount, or null to unmount.

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": {
      "id": "<id>",
      "os": "<os>"
    },
    "name": "vps_mount_iso"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
osYesISO identifier to mount, or null to unmount the current ISO

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that by disclosing a dual mode (mount vs. unmount via null), which an agent would otherwise have to infer. It stops short of saying whether the mount takes effect immediately, whether it disrupts a running VPS, or what state the machine must be in.

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?

Two short sentences, front-loaded with the operation and followed by the mode selection rule. There is no filler, and the dual-mode behavior is stated compactly in a single clause.

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?

The tool is simple (2 required params, no output schema, no nested objects), so the bar is low, and the annotations plus schema cover most of what an agent needs. The notable gap is discoverability of the ISO identifier — no sibling tool lists available ISOs, and the description doesn't say how to obtain a valid one or what happens on an invalid value.

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%, and the schema already documents 'os' as 'ISO identifier to mount, or null to unmount the current ISO' — the description restates this almost verbatim rather than adding meaning. Nothing is said about where a valid ISO identifier comes from or what format it takes beyond 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 uses a specific verb pair ('mount or unmount') and a specific resource ('an ISO image on a VPS'), so an agent knows exactly what the tool does. It doesn't need to distinguish itself from a close sibling (none of the listed siblings mount ISOs), but it also doesn't mention neighboring operations like vps_reinstall_os, which is a plausible confusion point.

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?

The second sentence explains how to select each of the tool's two modes ('pass an ISO identifier to mount, or null to unmount'), which implies usage but is really parameter guidance rather than when-to-use guidance. Nothing says under what conditions an agent should mount an ISO (rescue work? OS install?) or what prerequisites exist, and no alternatives are named.

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.