Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_set_tamper_protection

Enable or disable tamper protection on an endpoint to prevent unauthorized changes to Sophos agent settings, with optional password regeneration.

Instructions

Enable or disable tamper protection on an endpoint. When enabled, Sophos agent settings cannot be changed without the tamper protection password. Optionally regenerate the password.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYesSet to true to enable tamper protection, false to disable
tenant_idYesTarget tenant ID
endpoint_idYesEndpoint ID
regenerate_passwordNoWhether to generate a new tamper protection password
Behavior3/5

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

Discloses that enabling prevents changes without password, and mentions optional password regeneration. No annotations exist, so description is sole source; missing details like permissions required, side effects, or return behavior.

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?

Two sentences conveying essential information without unnecessary detail. Efficient and easy to parse.

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?

Adequate for a simple toggle action, but lacks output schema and details on error handling, permissions, or response structure. Could be more thorough given no annotations.

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 covers 100% of parameters with descriptions; description adds slight nuance about 'regenerate password' being optional, but does not provide significant extra meaning beyond 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?

Clear action (enable/disable) and resource (endpoint) explicitly stated. Differentiated from siblings like sophos_get_tamper_protection by specifying 'set' operation.

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?

No explicit when-to-use or alternatives mentioned. Context implies use for enabling/disabling tamper protection, but lacks guidance on when not to use or prerequisites.

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