uos-mcp

Overview Schema Source Related Servers Discussions Admin

vm_network_config

Enable or disable network access for a sandboxed VM, using user-mode NAT only. Changes apply at the next boot, so restart the VM to activate them.

Instructions

Set the VM's network flag: OFF by default; enabling needs the user's OK (RULES.md). Only user-mode NAT is implemented (bridge raises honestly). Applies at the next vm_boot - a running VM keeps its old network until shutdown + boot. Check with vm_status.

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>"
    },
    "name": "vm_network_config"
  }
}

Input Schema

Name	Required	Description	Default
`nat`	No
`name`	Yes
`enable`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Oct 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

No annotations, so the description must carry the behavioral burden. It discloses the default (OFF), the authorization requirement (user's OK), the implementation limitation (NAT only, bridge raises), the timing semantics (deferred to next boot), and the verification path (vm_status). This is substantial context for a 3-param mutation tool. Minor gap: no explicit mention of reversibility or failure behavior.

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?

Three sentences, front-loaded with the action and default, then implementation limits, then timing/verification. Efficient, though the parenthetical about bridge is slightly tangential.

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?

Output schema exists, so return values need not be explained. The description covers timing, authorization, and implementation limits, but omits parameter semantics (critical given 0% schema coverage) and any note on what happens if 'enable' is true without 'nat' or vice versa.

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 coverage is 0%, so the description must compensate. It mentions the 'network flag' and NAT but does not explain the three parameters (nat, enable, name) or their defaults/interactions. An agent cannot infer that 'enable' is the primary toggle and 'nat' selects network mode from the description alone.

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+resource (set the VM's network flag) and clarifies scope limitations (only NAT implemented, bridge unsupported). It distinguishes itself from runtime-control siblings like vm_boot by clarifying the config-vs-runtime relationship, though it doesn't name explicit alternatives.

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?

Explicitly defines when the change takes effect (next vm_boot, not a running VM) and points to vm_status for verification. It states a prerequisite (user's OK per RULES.md). Missing explicit pointers to alternative network tools, but usage context is clear.

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