Skip to main content
Glama
Sign In
Sophos Firewall MCP Server

Sophos Firewall MCP Server

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sophos_get_firewall_rule

Read-only

Retrieve full configuration details for a specific firewall rule by its name. Use this to inspect policy settings for a single rule.

Instructions

Retrieve details for a specific firewall rule by name.

Use when inspecting full policy configuration for a single firewall rule.

Args: name: Name of the firewall rule. client: Optional SophosFirewallClient instance.

Returns: Firewall rule configuration.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the firewall rule to retrieve.
clientNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Retrieve' aligns. No additional behavioral traits (e.g., error handling, permissions) are disclosed, but annotations cover the safety aspect sufficiently.

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?

The description is extremely concise: three sentences cover purpose, usage, and parameter definitions. No unnecessary words, and the most important info appears first.

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?

Given the tool's simplicity and the presence of an output schema, the description is complete enough. It covers the essential aspects: what, when, and parameters. Minor gap: no mention of behavior when rule not found, but not critical.

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?

The name parameter's description in both schema and description is redundant, but the client parameter lacks a schema description and the description adds 'Optional SophosFirewallClient instance', providing needed clarity beyond the schema.

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 explicitly states 'Retrieve details for a specific firewall rule by name', which is a clear verb+resource pairing. It distinguishes from sibling tools like list, create, update, and delete rules.

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?

Provides a clear use case: 'Use when inspecting full policy configuration for a single firewall rule.' Though it doesn't explicitly mention alternatives, the sibling set implies when not to use (e.g., for listing use list_firewall_rules).

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