Skip to main content
Glama

Create a firewall

create_firewall

Creates a reusable set of inbound and outbound rules. Without rules it starts with SSH (TCP 22) and ping open from anywhere; pass rules: [] for none. Nothing is filtered until it is attached to a machine. Scope: network.write.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name of the firewall, 1 to 64 characters.
rulesNoThe firewall's full list of rules, up to 50. What no rule opens is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Display name of the firewall, 1 to 64 characters."
    • addedInput schema / properties / rules / description
      Added value: +"The firewall's full list of rules, up to 50. What no rule opens is refused."
    • addedInput schema / properties / rules / items / properties / description / description
      Added value: +"Free note shown next to the rule, e.g. \"SSH from the office\"."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, open-world; the description adds materially more: the default permissive rules when rules is omitted (SSH TCP 22 and ping from anywhere), that an empty array means no rules, and the required permission scope network.write. It stops short of describing the returned object or how many rules are applied by default.

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?

Three tight sentences, front-loaded with purpose, then default behavior, then lifecycle caveat and scope. The trailing 'Scope: network.write' fragment is useful but abrupt; nothing is wasted.

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?

For a two-parameter creation tool with no output schema, this covers the risky unknowns (default open rules, inertness until attach). A short note on what the call returns, such as an identifier needed by attach_firewall, would close the remaining gap.

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 baseline is 3, but the description adds genuine meaning the schema lacks: the implicit defaults for the optional rules parameter and how to explicitly opt out with []. The name parameter gains nothing, but the important ambiguity is resolved.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource: 'Creates a reusable set of inbound and outbound rules.' It also implicitly separates itself from attach_firewall by noting 'Nothing is filtered until it is attached to a machine,' so the agent knows creation alone does not apply policy.

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 clear context for creation (reusable rule set, inert until attached) and the key edge case 'pass rules: [] for none.' It does not explicitly name update_firewall or delete_firewall as alternatives for later changes, so routing guidance is implied rather than exhaustive.

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.