Skip to main content
Glama
Sign In
portveil-mcp

portveil-mcp

by roybogs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Start rotation

start_rotation
Idempotent

Schedules recurring automatic VPN location moves for a Portveil device every N minutes, optionally among chosen locations; running it again replaces the existing schedule.

Instructions

Make Portveil move a device to the next location automatically every N minutes, optionally cycling through chosen locations only. Portveil runs the schedule itself, so the assistant doesn't need to stay running. Calling it again replaces the schedule. Stop it with stop_rotation. Needs a control-scope token and a Portveil-agent device.

Input Schema

NameRequiredDescriptionDefault
deviceYesWhich device: its name, a unique part of its name (e.g. "scraper"), or its device ID (dev_…). Case-insensitive. Get names and IDs from list_devices.
locationsNoLocations to cycle through, e.g. ["US", "Finland"]; at least two. Omit to cycle through every location.
every_minutesYesMinutes between moves: 5 to 10080 (one week)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.4
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the schedule is executed server-side so the assistant need not stay running, a repeat call replaces rather than stacks schedules, and control-scope plus agent-device requirements must be met. These are non-obvious operational facts an agent could not infer from readOnlyHint/idempotentHint.

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 tight sentences front-loading what happens, then lifecycle (replace/stop), then prerequisites. No filler and no repetition of annotation-declared safety facts.

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

Completeness5/5

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

For a scheduling mutation with no output schema, it covers persistence semantics, replacement behavior, the stop path, and auth/device prerequisites. An agent has everything needed to decide to call it and what to expect afterwards.

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 each parameter already documents format, bounds (5–10080), and the 'at least two' constraint. The description only restates the interval and the optional location subset, adding no syntax or edge-case detail beyond 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?

States a specific verb and resource: 'Make Portveil move a device to the next location automatically every N minutes'. The recurring/automatic framing plus 'optionally cycling through chosen locations only' clearly separates it from the one-off move_device and rotate_device siblings.

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 names the counterpart for teardown ('Stop it with stop_rotation') and states re-invocation replaces the schedule, plus prerequisites (control-scope token, Portveil-agent device). It stops short of directly contrasting with move_device/rotate_device, relying on 'automatically' to imply the distinction.

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