Skip to main content
Glama
Sign In
Sophos Firewall MCP Server

Sophos Firewall MCP Server

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sophos_list_service_groups

Read-only

List service group objects configured on Sophos Firewall to browse bundled services used in rule policies.

Instructions

List service group objects configured on Sophos Firewall.

Use when browsing bundled groups of services used in rule policies.

Args: name: Optional service group name filter. client: Optional SophosFirewallClient instance.

Returns: List or dict of service groups.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOptional service group name filter.
clientNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds that the tool lists objects and can filter by name, but does not disclose other behavioral aspects like pagination or rate limits. With annotations covering safety, a score of 3 is appropriate.

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?

Description is concise with a few sentences plus a structured docstring (Args/Returns). It is front-loaded with the purpose and usage context. Minor verbosity in the docstring could be trimmed, but overall well-structured.

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 presence of an output schema (not shown but indicated), the return description is adequate. The tool is simple with two optional params, and the description covers purpose and when to use. It could include more detail on client usage or response format, but is largely complete.

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% (name has description, client does not). The description adds meaning for both parameters, especially client ('Optional SophosFirewallClient instance'), which is missing from schema. However, the client parameter type is still vague.

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?

Description clearly states 'List service group objects configured on Sophos Firewall', specifying verb and resource. This distinguishes it from sibling tools like sophos_list_services (individual services) and sophos_list_ip_host_groups (IP host groups).

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 explicit context for when to use the tool: 'Use when browsing bundled groups of services used in rule policies.' This helps an agent decide, though it does not explicitly mention when not to use or list alternatives.

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