Skip to main content
Glama

Change VPS firewall

vps_manage_firewall
Destructive

Change a VPS's host firewall over SSH. add_rule and remove_rule need port, proto and ruleAction; remove_rule must match a rule from vps_get_firewall. enable keeps the SSH port open by itself; add rules for every other port in use first (web 80 and 443, game or database ports), or those services become unreachable. disable stops all filtering. Needs ufw, firewalld or Windows Firewall on the VPS; without one the call fails.

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "vps_manage_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID
portNoPort or port range (e.g. '80', '8000:8100'). Required for add_rule and remove_rule.
protoNoProtocol. Required for add_rule and remove_rule.
actionYesadd_rule or remove_rule for one rule; enable or disable for the whole firewall
sourceNoSource IP/CIDR or 'any' (default: 'any')
commentNoOptional comment for the rule
ruleActionNoAllow or deny. Required for add_rule and remove_rule.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already mark this as non-read-only and destructive, but the description adds substantial context beyond them: operations happen over SSH, enable keeps SSH open but can make other services unreachable unless rules are added first, disable stops all filtering, and the call fails without ufw, firewalld, or Windows Firewall.

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?

The description is front-loaded and efficient, covering actions, prerequisites, and warnings in a compact block. It repeats some action-specific schema requirements, but that repetition reinforces safe usage rather than creating noise.

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 destructive, seven-parameter management tool with no output schema, the description provides the operational context an agent needs: dependencies, action-specific requirements, and the unreachability risk of enabling the firewall without adding rules. No critical invocation detail appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents parameter types, defaults, and required fields. The description adds useful meaning beyond the schema by explaining that remove_rule must match a rule from vps_get_firewall and by emphasizing which parameters are required for which actions.

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?

The description states a specific verb and resource: changing a VPS's host firewall over SSH. It names the four supported actions and explicitly points to vps_get_firewall as the source of rules for remove_rule, so an agent can distinguish it from the sibling tool.

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?

It gives clear action-specific guidance: add_rule and remove_rule require port, proto, and ruleAction; remove_rule must match an existing rule obtained via vps_get_firewall. It also warns that enabling requires adding rules for non-SSH ports first or those services become unreachable, and states the prerequisite firewall software.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.