Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_search_quarantine

Read-only

Search pre-delivery quarantine messages using structured filters. Filter by date, reason, sender, recipient, subject, attachment, and more to find specific 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?

Annotations already declare readOnlyHint and destructiveHint. Description adds no behavioral context beyond 'search' and 'list'. No mention of pagination, date range behavior, or rate limits.

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?

Two sentences, front-loaded with key purpose. No unnecessary words. Efficiently communicates the core function.

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 13 parameters and no output schema, description is adequate but could mention output structure (list of quarantined messages) and pagination behavior. Sufficient for basic understanding.

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% so parameters are fully described. Description does not add any extra meaning beyond the schema. Baseline 3.

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?

Clearly states verb 'search', resource 'pre-delivery quarantine messages', and mentions 'structured filters'. Differentiates from sibling tools like sophos_search_post_delivery_quarantine and other quarantine tools.

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 on when to use this tool vs alternatives. Only says 'primary way to list quarantined messages' but doesn't explain when to use other search or retrieval tools.

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