Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_quarantine_attachments

List all attachments from a pre-delivery quarantined message, enabling security review of potential threats before the email is released.

Instructions

List attachments of a pre-delivery quarantined message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenant_idYesTenant UUID
message_idYesQuarantine message UUID
Behavior2/5

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

No annotations provided. Description implies read-only behavior but lacks details on pagination, limits, permissions required, or side effects. Minimal addition beyond the tool name.

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?

Single, concise sentence that front-loads the key action and resource. Could include more context without becoming verbose, but current length is appropriate.

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?

Adequate for a simple list operation with only two parameters and no output schema. However, lacks details on return format, pagination, or required permissions. Sibling tools with similar names could cause confusion without more context.

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 baseline is 3. Description adds 'pre-delivery' context but does not explain parameter semantics beyond what the schema already provides (e.g., tenant_id is a UUID, message_id is a quarantine message UUID).

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 the specific action (list), resource (attachments), and context (pre-delivery quarantined message). Distinguishes from siblings like sophos_list_post_delivery_quarantine_attachments and sophos_download_quarantine_attachments.

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 versus alternatives like download or search. Does not mention prerequisites (e.g., obtaining message_id from a prior list) or provide when-not-to-use instructions.

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