Skip to main content
Glama
Sign In
portveil-mcp

portveil-mcp

by roybogs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Rotate device

rotate_device

Moves a device once to the next VPN location in the list, changing where its traffic exits. Each call advances again; use start_rotation for repeated automatic moves.

Instructions

Move a device once to the next location in the list, so its traffic exits from somewhere new. Same checks and waiting as move_device. Each call moves again, so it isn't idempotent. For repeated automatic moves use start_rotation instead. Needs a control-scope token.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.4
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / device / description
      Previous value: -"Device name (or part of it, e.g. \"scraper\") or its device ID (dev_…)"New value: +"Which 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."
  3. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Adds context beyond annotations: "Same checks and waiting as move_device" discloses a preflight-check plus async-wait pattern, and "Needs a control-scope token" discloses an auth requirement that appears nowhere in the structured fields. The non-idempotency note restates idempotentHint=false, and it does not say what happens when checks fail or how long the wait takes.

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?

Five short sentences, front-loaded with the action and effect, then constraints and the alternative. Every sentence carries distinct information; nothing is padding.

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

Completeness4/5

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

Covers action, idempotency, auth scope, and sibling routing for a one-parameter tool. With no output schema, it would ideally state what is returned after the move (e.g., the new location), but the "traffic exits from somewhere new" framing covers the essential outcome.

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?

Single parameter with 100% schema description coverage; the schema already explains name/partial-name/device-ID matching, case-insensitivity, and where to obtain values. The description adds no parameter-level meaning, which is acceptable at this coverage level.

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 ("Move a device once to the next location in the list") with the observable effect ("traffic exits from somewhere new"). It is clearly distinguishable from move_device (targeted move) and start_rotation (repeated moves) without needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the alternative: "For repeated automatic moves use start_rotation instead," which is exactly the decision an agent faces among these siblings. It also implies a one-shot vs. targeted split against move_device via "same checks and waiting as move_device."

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