Skip to main content
Glama

Rename a firewall or replace its rules

update_firewall
DestructiveIdempotent

rules REPLACES the whole list and is applied at once to every attached machine: send every rule to keep, not only the new one (read get_firewall first). Removing the SSH rule can lock the agent out. pending_machines counts machines not updated yet, retried automatically. 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": {
      "firewall": "<firewall>"
    },
    "name": "update_firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew display name; omitted, the name is kept.
rulesNoThe firewall's full list of rules, up to 50. What no rule opens is refused.
firewallYesFirewall id, as returned by list_firewalls or create_firewall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"New display name; omitted, the name is kept."
    • 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.2/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds substantial context beyond them: full-list replacement semantics, immediate application to all attached machines, the pending_machines retry behavior, the SSH lockout hazard, and the required network.write scope. This is exactly the behavioral detail an agent needs before a destructive call.

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?

Dense and front-loaded, leading with the most consequential fact (full replacement). The telegraphic style ('rules REPLACES...') is efficient, though the abrupt fragments and mid-sentence scope tag make it slightly harder to parse than flowing prose.

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 destructive, open-world mutation with no output schema, the description covers the key risks, retry behavior, and required scope. The only gap is that the rename path is only conveyed by the title, not the description body.

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 meaning the schema does not: that rules is a complete replacement list rather than an append, and that every rule to keep must be resent. That is a critical semantic distinction not encoded in the schema.

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?

The description states a specific verb and resource behavior: 'rules REPLACES the whole list and is applied at once to every attached machine.' Combined with the title's 'Rename a firewall or replace its rules,' an agent can identify the operation. The description itself never mentions the rename capability, leaving that to the title.

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?

It gives an explicit prerequisite ('read get_firewall first') and a concrete warning about when this is dangerous ('Removing the SSH rule can lock the agent out'). It does not distinguish this tool from the sibling set_rules, so the alternative-selection guidance is incomplete.

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.