Skip to main content
Glama

firewall

Read-onlyIdempotent

Inspect selected security rules in read-only mode; no rule changes are available, supporting review of network access controls.

Instructions

Inspect selected firewall rules; no rule changes are available.

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": "firewall"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully handled by structured data. The description's only added disclosure is the reiteration that changes are unavailable; it says nothing about what "selected" means, whether results reflect running vs. persisted config, or any auth/rate considerations.

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?

A single compact sentence with the inspection intent front-loaded and the read-only constraint immediately following. No filler, no repetition of the tool name.

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 zero-parameter, non-destructive inspection tool with full annotation coverage and no output schema, this is close to sufficient. The one residual gap is the unexplained "selected," but little else is required to invoke it correctly.

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?

With zero parameters the baseline would normally be 4, but the description's wording implies a selection or filtering concept that has no corresponding input, leaving an unexplained gap an agent may try to resolve. It therefore adds ambiguity rather than meaning beyond the (empty) 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?

States a specific verb and resource ("Inspect ... firewall rules") and explicitly bounds scope with "no rule changes are available," which separates it from any configuration-mutation tools in the sibling list. The qualifier "selected" is left unexplained, which slightly blunts precision for a tool with zero parameters.

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

Usage Guidelines3/5

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

The clause "no rule changes are available" tells the agent this is not the place to attempt modifications, which is a useful boundary. However, it gives no positive trigger for when to reach for this tool over node_status or storage_status, and no prerequisites or exclusions beyond the negative statement.

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