Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_delete_post_delivery_quarantine_messages

Remove post-delivery quarantined email messages from a Sophos tenant by providing tenant UUID and message IDs.

Instructions

Delete one or more post-delivery quarantined messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_idYesTenant UUID
message_idsYesArray of post-delivery quarantine message IDs to delete
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits like irreversibility, required permissions, or side effects. For a delete operation, critical details are missing beyond the basic action.

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 extremely concise (one sentence) and front-loaded with the verb. No unnecessary words. Effectively communicates the essential purpose with minimal text.

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 tool is simple with only two inputs and no output schema. The description covers the basic purpose but lacks behavioral context and guidance. It is adequate but not comprehensive.

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 coverage is 100% (both parameters have descriptions). The description adds no additional meaning beyond the schema, so 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), the target resource (post-delivery quarantined messages), and specifies it can handle multiple messages. It distinguishes itself 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 Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as sophos_release_post_delivery_quarantine_messages or sophos_delete_quarantine_messages. There is no context for appropriate use cases 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