Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_mobile_action_wipe

Remotely wipe up to 50 mobile devices, erasing all data. Use with extreme caution—operation cannot be undone. Macs require a 6-digit wipe code.

Instructions

DESTRUCTIVE: Remotely wipe up to 50 mobile devices, erasing all data. Use with extreme caution — this operation cannot be undone. Macs require a 6-digit wipe code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_idYesTenant UUID
wipe_codeNo6-digit wipe code — required for Macs
endpoint_idsYesComma-separated device UUIDs (max 50)
preserve_data_planNoPreserve configured data plans (e.g. eSIM) — iOS only
disallow_proximity_setupNoDisallow proximity setup after wipe — iOS only
Behavior3/5

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

No annotations provided, so description must cover behaviors. It discloses destructive, irreversible nature and Mac wipe code requirement. However, it omits permissions, rate limits, default behavior for non-Macs without wipe_code, and does not explain what happens to endpoint_ids that fail.

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?

Two sentences, front-loaded with 'DESTRUCTIVE', concise and informative. Every sentence adds value without fluff.

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?

For a destructive tool with 5 params and no output schema, the description covers core behavior and Mac requirement but lacks details on OS-specific differences, error handling, rate limits, and prerequisite permissions. Schema partially compensates.

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 100%, so baseline is 3. The description adds context about wipe_code for Macs but does not enhance understanding of other parameters beyond schema. It repeats the 'up to 50' from 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 the action 'wipe' the resource 'mobile devices' with scope 'up to 50', and the first word 'DESTRUCTIVE' emphasizes severity. This distinguishes it from sibling tools like lock or locate.

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 warns of extreme caution and irreversibility, but does not clarify when to wipe vs. other actions (e.g., lock or unenroll). It 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rijul170/sophos-central-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server