Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_release_quarantine_messages

Release pre-delivery quarantined messages to recipients. Optionally allow sender or submit messages to Sophos Labs for analysis.

Instructions

Release one or more pre-delivery quarantined messages to recipients. Optionally allow sender or submit to labs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_idYesTenant UUID
message_idsYesArray of quarantined message IDs to release
allow_senderNoAdd sender to allow list
submit_to_labsNoSubmit message to Sophos Labs for analysis
enforce_sender_authenticationNoEnforce sender authentication
Behavior2/5

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

With no annotations, the description only states the action and optional parameters without disclosing side effects, reversibility, or state changes beyond the minimal 'release'.

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 a single, efficient sentence that front-loads the action and resource, with no wasted 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 is adequate for a straightforward release action but lacks details on response, success indicators, or any behavioral context beyond the action itself.

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?

The schema covers 100% of parameters with descriptions, and the description adds no additional parameter information beyond what is already in the schema, meeting the baseline.

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 uses the verb 'release' and the resource 'pre-delivery quarantined messages', distinguishing it from siblings like sophos_delete_quarantine_messages and sophos_release_post_delivery_quarantine_messages.

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 implies it is for pre-delivery quarantine messages and mentions optional actions but does not explicitly state when to use vs alternatives or provide exclusions 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