Skip to main content
Glama
Systems Manager

Systems Manager

Add Firewall Rule

sm_firewall_add_firewall_rule
Destructive

Adds a structured firewall rule to allow or deny traffic by protocol, port, direction, and optional source or destination, with an explicit confirmation flag for mutating changes.

Instructions

Add firewall rule (sm_firewall_operations). Operations for firewall management

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_firewall_add_firewall_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleNoStructured firewall rule specification
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top: it does not say what the rule affects, whether it is additive to an existing ruleset, what happens on duplicate names, or anything about the confirm approval flow described in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than concision. The one substantive clause duplicates the title, and the trailing 'Operations for firewall management' occupies space without conveying information.

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

Completeness2/5

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

This is a destructive mutation with no output schema; the description should explain effect, scope, and confirmation behavior. The annotations carry the safety hint, but an agent still cannot tell from the description what creating a rule does to the live ruleset or when confirmation is required.

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%, with rich per-field descriptions (name pattern, port range, action/protocol enums, direction default), so the baseline is 3 even though the description says nothing about parameters. The description neither reinforces nor clarifies the nullable 'rule' object or the 'confirm' flag.

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

Purpose2/5

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

The description is essentially a restatement of the tool name and title: 'Add firewall rule' adds no verb nuance, scope, or target beyond 'sm_firewall_add_firewall_rule' / 'Add Firewall Rule'. The parenthetical '(sm_firewall_operations)' is an internal tag, and the second sentence 'Operations for firewall management' merely names a namespace. Nothing distinguishes it from the sibling sm_firewall_remove_firewall_rule beyond the obvious opposite verb.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or the ordering relationship with sm_firewall_remove_firewall_rule or sm_firewall_get_firewall_status. An agent must infer everything from the name alone.

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