Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_delete_quarantine_messages

Delete pre-delivery quarantined messages and optionally block the sender to stop future threats.

Instructions

Delete one or more pre-delivery quarantined messages. Optionally block sender.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_idYesTenant UUID
message_idsYesArray of quarantined message IDs to delete
block_senderNoAdd sender to block list
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the destructive action and optional block sender, but does not disclose whether deletion is irreversible, required permissions, rate limits, or side effects beyond blocking sender.

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?

The description is concise (one sentence, 8 words) and front-loaded with the action and resource. It is efficient but could benefit from a bit more detail for completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description lacks details on return values, prerequisites (e.g., obtaining message IDs), and error handling. It is minimally adequate for a simple delete but incomplete for robust decision-making.

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 the schema already documents all parameters. The description adds no new meaning beyond stating the optional block sender, which is already in the schema. Baseline score of 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 clearly states the action ('delete') and the resource ('pre-delivery quarantined messages') with an optional side effect ('block sender'). It differentiates from sibling 'sophos_delete_post_delivery_quarantine_messages' by specifying 'pre-delivery'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context for usage. It simply states what it does without any situational advice.

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