Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_search_quarantine

Search pre-delivery quarantine messages using structured filters (sender, recipient, subject, attachment, direction, reason) to list quarantined emails.

Instructions

Search pre-delivery quarantine messages with structured filters. This is the primary way to list quarantined messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort fields, e.g. ['quarantinedAt:DESC']
end_dateNoEnd date ISO 8601
page_sizeNoResults per page (max 200)
tenant_idYesTenant UUID
begin_dateNoStart date ISO 8601 (e.g. 2024-01-01T00:00:00.000Z)
filter_reasonNoFilter by quarantine reason (e.g. ['impersonation','spam','malware'])
page_from_keyNoPagination key from previous response
filter_directionNoFilter by message direction
filter_to_containsNoFilter: recipient address contains
filter_from_containsNoFilter: sender address contains
filter_has_attachmentNoFilter messages that have attachments
filter_subject_containsNoFilter: subject contains
filter_attachment_name_containsNoFilter: attachment name contains
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Search pre-delivery quarantine messages with structured filters', which is vague. It does not mention that the operation is read-only, that results are paginated (though schema hints), or any side effects or authentication requirements.

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 two sentences long and front-loaded with the core action. Every sentence adds value: it specifies the resource type (pre-delivery) and positions the tool as the primary listing method. No unnecessary 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?

Given the tool has 13 parameters and no output schema, the description provides only the basic purpose. It does not explain the return format (e.g., list of messages), pagination behavior, or error conditions. It is adequate but lacks detail for a complex search tool.

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 description coverage is 100%, meaning all 13 parameters have descriptions in the schema. The tool description adds no additional information about parameters. According to the rule, baseline is 3 when coverage is high.

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 uses the specific verb 'Search' and identifies the resource as 'pre-delivery quarantine messages', which distinguishes it from sibling tools like sophos_search_post_delivery_quarantine. The phrase 'primary way to list quarantined messages' further clarifies its role.

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 states 'This is the primary way to list quarantined messages', implying it should be used for listing. However, it does not explicitly mention when not to use it or provide comparisons with alternative tools such as sophos_get_quarantine_message or sophos_search_post_delivery_quarantine.

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