Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_search_alerts

Search and filter alerts using a POST request body with filters like severity, product, category, date range, or alert IDs. Enables complex queries for targeted alert retrieval.

Instructions

Search alerts using a POST request body. Equivalent to sophos_list_alerts but filters are sent in a JSON body — useful for filtering by multiple IDs or long lists of categories/products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoArray of specific alert IDs to retrieve
sortNoSort order array (e.g. ['raisedAt:desc'])
fieldsNoFields to include in the response (e.g. ['severity', 'groupKey', 'allowedActions'])
productNoArray of product names to filter on (e.g. ['endpoint', 'server', 'mobile', 'wireless'])
to_dateNoReturn alerts raised before this ISO 8601 timestamp
categoryNoArray of alert categories to filter on (e.g. ['malware', 'policy', 'runtimeDetections'])
page_keyNoPagination key for fetching the next page of results
severityNoArray of severity levels to filter on (e.g. ['high', 'medium', 'low'])
from_dateNoReturn alerts raised after this ISO 8601 timestamp
group_keyNoFilter by group key for grouped alerts
page_sizeNoNumber of alerts per page (default 50)
tenant_idYesThe tenant ID to search 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?

No annotations are provided, so the description must disclose behavioral traits. It mentions the HTTP method (POST) and that filters are sent in a JSON body, but it does not address permissions, side effects, rate limits, or whether the operation is read-only. This leaves significant gaps for safe and correct invocation.

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: two sentences, no wasted words. The first sentence front-loads the core purpose and method, the second provides the key use case and comparison. Every sentence earns its place.

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 tool has 13 parameters and no output schema or annotations, the description is too brief. It does not cover pagination, parameter interdependencies, or the response format. The agent must rely solely on the schema for parameter details, and lacks guidance on how to structure the JSON body or interpret results.

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 baseline is 3. The description adds value by hinting that parameters like 'ids', 'category', and 'product' are useful for long lists, but it does not elaborate on parameter constraints or relationships. The schema itself already documents each parameter sufficiently.

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 'Search alerts using a POST request body' and explicitly compares to sophos_list_alerts, distinguishing it as the variant for sending filters in a JSON body. This provides a specific verb (search) and resource (alerts) with differentiation from a sibling tool, earning the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description explains when to use this tool: 'useful for filtering by multiple IDs or long lists of categories/products', and explicitly mentions sophos_list_alerts as the alternative. While it doesn't list all alternatives or state when not to use, the context is clear enough to guide tool selection.

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