Skip to main content
Glama
Sign In
vm-relay

vm-relay

by WeZZard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Extract declared outputs

relay_extract

Pull declared extraction outputs from a guest VM early by name. Only outputs declared on relay_acquire can be pulled; each pull verifies hashes and blocks traversal, symlinks, or changed sources.

Instructions

Pull one or more already-declared extraction outputs home early, by names. Only outputs declared on relay_acquire may be pulled; each pull verifies source and host hashes and rejects path traversal, symlinks, or a source that changed underneath it.

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": {
      "guest": "<guest>",
      "names": "<names>"
    },
    "name": "relay_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestYesThe guest this call acts on: the name relay_acquire answered.
namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.0
    • addedInput schema / properties / guest
      Added value: +{
+  "description": "The guest this call acts on: the name relay_acquire answered.",
+  "pattern": "^[a-z0-9][a-z0-9-]{0,47}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "names"
-]New value: +[
+  "guest",
+  "names"
+]
  2. Addedv0.5.1

TDQS

A4.1/5.0
Behavior4/5

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

With annotations already declaring readOnly=false, destructive=false, idempotent=false, openWorld=false, the description adds real behavioral context: each pull verifies source and host hashes and rejects path traversal, symlinks, or a source that changed underneath it. It does not say where outputs land ('home' is vague) or what failure/success looks like, but the validation and security behavior is genuinely beyond the annotations.

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 sentences, action front-loaded, followed by the prerequisite and the safety/rejection behavior. No sentence is wasted.

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?

There is no output schema, so the description should explain the return surface, but it never says what the agent gets back (paths, files, status) or what 'home' concretely means. For a 2-param retrieval tool this is a noticeable gap, though the safety and prerequisite coverage offsets part of it.

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 coverage is 50%: `guest` is documented in the schema, but `names` has no schema description. The tool description partially compensates by establishing that `names` refers to outputs declared on relay_acquire and that multiple may be pulled at once, but it adds no format or constraint detail for the array. Baseline 3 for the partial coverage gap.

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?

States a specific verb (pull), resource (already-declared extraction outputs), and scoping mechanism (by `names`). It distinguishes itself from the sibling that declares outputs by noting 'Only outputs declared on relay_acquire may be pulled', so an agent can tell it apart from relay_acquire without opening either schema.

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?

Gives a clear usage context ('home early', i.e., retrieving outputs before the normal completion flow) and a hard prerequisite tying it to relay_acquire. It stops short of explicitly naming alternatives (relay_finish/relay_release) or stating when NOT to use it, so it is context-rich but not fully exhaustive.

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