Skip to main content
Glama
Sign In
Sophos Firewall MCP Server

Sophos Firewall MCP Server

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sophos_get_nat_rule

Read-only

Retrieve detailed configuration of a specific NAT rule to audit original and translated source, destination, and service parameters.

Instructions

Retrieve detailed configuration of a specific NAT rule.

Use when auditing original/translated source, destination, and service parameters.

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

Returns: NAT rule configuration details.

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_nat_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the NAT rule to retrieve.
clientNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that it retrieves 'detailed configuration,' implying no side effects. No behavioral traits beyond this are disclosed, but the annotation covers the main aspect.

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 concise with two sentences for purpose and usage, followed by arg/return details. It is front-loaded with the key action and avoids redundancy or filler.

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

Completeness5/5

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

Given the existence of an output schema and annotations, the description adequately explains the tool's purpose and key parameters. It mentions relevant audit parameters (source, destination, service) and is complete for a read operation.

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 description coverage is 50% (name has description, client lacks). The description clarifies that client is 'Optional SophosFirewallClient instance,' adding meaning beyond the schema's 'Client' title. For name, it restates the schema but is consistent.

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 clearly states 'Retrieve detailed configuration of a specific NAT rule,' specifying the verb (retrieve) and resource (NAT rule). It differentiates from siblings like sophos_list_nat_rules (list all) and sophos_create_nat_rule (create), ensuring distinct purpose.

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?

The description provides a specific use case: 'Use when auditing original/translated source, destination, and service parameters.' It does not explicitly state when not to use or list alternatives, but the context is sufficiently clear given sibling tools.

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