uos-mcp

by Jenischristan

Overview Schema Source Related Servers Discussions Admin

Python

Local

vm_get_file

Pull a file from the guest VM to your local machine for analysis, including traces, dumps, and test logs.

Instructions

Pull a file out of the guest (e.g. an .etl trace, a crash dump, a test log).

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>",
      "guest_path": "<guest_path>",
      "local_path": "<local_path>"
    },
    "name": "vm_get_file"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`guest_path`	Yes
`local_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Oct 3, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and falls well short. It does not disclose that the VM must be running, that the operation writes to the host filesystem (local_path), whether existing files are overwritten, or any permission/authentication requirements.

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?

A single front-loaded sentence with no wasted words; the action is stated before the examples. It is appropriately sized, though its brevity reflects under-specification rather than disciplined economy.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be explained, but with zero annotations, 0% parameter coverage, and three required params, the description leaves critical gaps: prerequisites, host-side side effects, and parameter meanings are all absent.

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?

All three required parameters (name, guest_path, local_path) have 0% schema description coverage, so the description must compensate and largely does not. 'Pull a file out of the guest' weakly implies guest_path is the source and local_path the destination, but 'name' is entirely unexplained and no path format is given.

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 states a specific verb ('Pull') and resource ('a file') with a clear source/destination relationship ('out of the guest'), and the examples (.etl trace, crash dump, test log) concretely illustrate what kind of files. It does not explicitly name the inverse sibling vm_put_file, so differentiation is only implicit.

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 examples hint at a post-test/post-run retrieval scenario, but there is no explicit statement of when to use this versus vm_put_file, vm_exec, or vm_log, and no prerequisites or exclusions are given. The agent must infer the usage context.

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