Skip to main content
Glama
Sign In
Sophos Firewall MCP Server

Sophos Firewall MCP Server

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sophos_delete_service_group

DestructiveIdempotent

Delete an obsolete service group from Sophos Firewall by specifying its name to clean up outdated configurations.

Instructions

Delete a service group object by name.

Use when removing an obsolete service group definition from Sophos Firewall.

Args: name: Name of the service group to remove. client: Optional SophosFirewallClient instance.

Returns: API response status dictionary.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the service group to remove.
clientNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description confirms deletion. Beyond that, no additional behavioral context is provided (e.g., irreversibility, permissions, or side effects). No contradiction with annotations.

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?

The description is well-structured with a one-liner, usage sentence, and clear Args/Returns sections. It is concise but slightly redundant (usage sentence could merge with action). No wasted sentences.

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

Completeness3/5

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

Given the simple tool type (delete) and presence of annotations and output schema, the description is adequate but leaves out prerequisites (e.g., service group must exist) and error conditions. The usage guidance is minimal. Completeness is acceptable but not thorough.

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 50% (only name has a description). The description adds value by documenting the optional client parameter as 'Optional SophosFirewallClient instance', which the schema lacks. It also restates the name parameter's purpose, adding no new info but maintaining clarity.

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 the action (Delete), the resource (service group), and the identifier (by name). It distinguishes from sibling tools like sophos_delete_service and sophos_delete_ip_host_group by specifying 'service group'.

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 description includes a usage sentence: 'Use when removing an obsolete service group definition from Sophos Firewall.' This provides context but does not mention when not to use the tool or suggest alternatives (e.g., listing first). No exclusions are stated.

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