Skip to main content
Glama

Get VPS firewall

vps_get_firewall
Read-only

Read a VPS's host firewall over SSH: which tool runs it (ufw, firewalld or Windows Firewall), whether it is active, the default incoming and outgoing policies and the rules. Read it before vps_manage_firewall to see which ports are open. readViaSSH false means the VPS could not be reached and the values are defaults, not the real state.

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>"
    },
    "name": "vps_get_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the access channel (over SSH) and a critical failure mode: "readViaSSH false means the VPS could not be reached and the values are defaults, not the real state." That caveat prevents an agent from acting on stale default values, which is meaningful behavioral context the annotations cannot carry.

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: purpose and returned fields first, then the alternative tool, then the failure-mode caveat. No filler, and the most decision-relevant information is front-loaded.

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?

With no output schema, the description compensates by enumerating the return fields an agent will see, plus the readViaSSH flag semantics. For a single-parameter read tool, nothing needed to call it correctly or interpret results is missing.

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?

There is only one parameter (id) and schema description coverage is 100%, so the schema already documents it fully. The description adds no additional parameter-level meaning, which matches the baseline of 3 when the schema does the heavy lifting.

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 uses a specific verb ("Read") and a specific resource ("a VPS's host firewall over SSH"), then enumerates exactly what is reported: which tool runs it (ufw, firewalld, Windows Firewall), whether it is active, default incoming/outgoing policies, and the rules. It also implicitly distinguishes itself from the mutation sibling vps_manage_firewall.

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 an explicit sequencing instruction: "Read it before vps_manage_firewall to see which ports are open," naming the alternative tool and the condition that selects it. An agent knows both when to call this and what to call next.

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.