Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_alerts

Retrieve and filter security alerts from Sophos Central by tenant, severity, product, category, and date range, with pagination support.

Instructions

List alerts from Sophos Central for a given tenant, with optional severity, product, category, date range, and pagination filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of specific alert IDs to retrieve
sortNoSort order (e.g. 'raisedAt:desc')
productNoComma-separated product names to filter on (e.g. 'endpoint,server,wireless,mobile')
to_dateNoReturn alerts raised before this ISO 8601 timestamp
categoryNoComma-separated alert categories to filter on (e.g. 'malware,policy,runtimeDetections,applicationControl')
page_keyNoPagination key for fetching the next page of results
severityNoComma-separated severity levels to filter on (e.g. 'high,medium,low')
from_dateNoReturn alerts raised after this ISO 8601 timestamp
page_sizeNoNumber of alerts per page (default 50)
tenant_idYesThe tenant ID to query alerts for
page_totalNoIf true, include total page count in the response
Behavior2/5

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

With no annotations provided, the description must fully convey behavioral traits. It does not mention important aspects such as pagination behavior (though parameters suggest pagination), response format, rate limits, authentication requirements, or side effects. The description is minimal and does not disclose what happens when no alerts are found or how errors are handled.

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 a single sentence of 20 words, front-loaded with the main action ('List alerts from Sophos Central for a given tenant') and then listing optional filters. Every word contributes to understanding the tool's purpose. There is no redundancy or unnecessary detail.

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 the complexity (11 parameters, no output schema, no annotations), the description is insufficient. It does not describe the return value (e.g., list of alert objects), pagination semantics, or error conditions. The description only covers input aspects, leaving the agent unaware of output structure or behavioral nuances.

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 input schema has 100% description coverage, so the schema already documents each parameter well. The description adds a high-level summary of filter categories (severity, product, etc.) but does not provide additional meaning beyond what the schema contains. Baseline score of 3 is appropriate as the description adds no new semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (list) and resource (alerts) with a specific scope (for a given tenant). It lists several filter types, making the purpose specific. However, it does not explicitly differentiate from the sibling tool 'sophos_search_alerts' or 'sophos_get_alert', so it lacks distinctiveness from similar 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?

The description provides no guidance on when to use this tool versus alternatives like 'sophos_search_alerts' or 'sophos_get_alert'. There is no mention of prerequisites, limitations, or scenarios where this tool is preferred. The description is purely declarative without usage direction.

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