Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_search_alerts

Read-only

Retrieve alerts filtered by multiple criteria including IDs, categories, products, and severity via a POST request with JSON body.

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
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, destructiveHint. Description adds method (POST) and equivalence to list_alerts but no additional behavioral traits like pagination or response format.

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, no redundancy, front-loaded with verb and resource.

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?

With 13 parameters and no output schema, description lacks details on pagination, response structure, or how filters combine. Annotations cover safety but not operational completeness.

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 applies. Description adds context about JSON body and large filters but does not enhance individual parameter understanding beyond schema.

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?

Description explicitly states 'Search alerts using a POST request body' and distinguishes from sibling 'sophos_list_alerts' by noting the method difference and use case for long filter lists.

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?

Clearly indicates when to use: 'useful for filtering by multiple IDs or long lists'. Implies alternative for simpler filters but does not explicitly state when not to use.

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