Skip to main content
Glama
Sign In
Sophos Firewall MCP Server

Sophos Firewall MCP Server

by jelmervdm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

sophos_delete_user

DestructiveIdempotent

Delete a local user account by username to remove obsolete or revoked accounts from Sophos Firewall.

Instructions

Delete a local user account by username.

Use when removing obsolete or revoked user accounts from Sophos Firewall.

Args: username: Username of the account to delete. 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": {
      "username": "<username>"
    },
    "name": "sophos_delete_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientNo
usernameYesUsername of the user account to remove.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds no additional behavioral details such as what happens if the user does not exist, whether deletion is reversible, or any side effects.

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 and well-structured: a purpose line, usage note, parameter list, and return value. No unnecessary words.

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?

The description covers basic purpose and usage but lacks details on error handling, idempotency behavior, and permissions. Given the presence of an output schema and annotations, it is minimally adequate but not thorough.

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 description coverage is 50%; the description adds some context for the 'client' parameter ('Optional SophosFirewallClient instance'), but the meaning of 'client' remains vague. The 'username' parameter description adds little 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 clearly states 'Delete a local user account by username.' The verb 'delete' and resource 'local user account' are specific. This distinguishes it from sibling tools like create_user or list_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 provides explicit usage context: 'Use when removing obsolete or revoked user accounts from Sophos Firewall.' It does not mention alternatives or when not to use, but the guidance is clear.

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