Sophos Firewall MCP Server

Overview Schema Source Related Servers Discussions Admin

sophos_list_users

Read-only

Retrieve local user accounts configured on Sophos Firewall. Optionally filter by username to browse specific accounts and their group memberships.

Instructions

List local user accounts configured on Sophos Firewall.

Use when browsing local user accounts and group memberships.

Args: username: Optional username filter. client: Optional SophosFirewallClient instance.

Returns: List or dict of user accounts.

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

Input Schema

Name	Required	Description	Default
`client`	No
`username`	No	Optional username filter.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior2/5

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

The annotation already declares readOnlyHint=true, and the description adds nothing beyond 'List' to indicate safety. There is no mention of side effects, required permissions, or rate limits. The description adds minimal behavioral context beyond the annotation.

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 very concise: one sentence for purpose, one for usage, then Args and Returns. Every element earns its place with no fluff.

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 (list operation), presence of output schema, and readOnlyHint annotation, the description covers the key aspects: what it lists, when to use it, and parameter details. Minor gaps like pagination or default behavior are acceptable for a simple list tool.

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?

Schema coverage is 50% (client parameter undescribed). The description adds some meaning: for username, it repeats 'Optional username filter'; for client, it says 'Optional SophosFirewallClient instance.' This adds value but does not fully compensate for the missing schema description. Baseline 3 is appropriate.

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 'List local user accounts configured on Sophos Firewall,' using a specific verb and resource. It distinguishes from siblings like 'sophos_list_live_users' by specifying 'local' users.

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 says 'Use when browsing local user accounts and group memberships,' providing clear context. It implicitly distinguishes from live users via the 'local' qualifier but lacks explicit when-not-to-use guidance or alternatives.

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

Deploy Server