Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_start_detections_query

Start an asynchronous detection query to retrieve security events from a Sophos tenant. Specify time range, severity, or detection rule; then poll status to obtain results.

Instructions

Start an async detections query run. Returns a run ID. Poll sophos_get_detections_query_status until status is 'finished', then retrieve results with sophos_get_detections_query_results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order for results. E.g. [{field: 'severity', direction: 'desc'}]
to_dateNoEnd of the time range in ISO 8601 format
severityNoArray of integer severity scores to filter on (1–10). E.g. [7,8,9,10] for high severity.
from_dateNoStart of the time range in ISO 8601 format (e.g. '2024-01-01T00:00:00.000Z')
tenant_idYesTenant UUID
detection_ruleNoFilter by a specific detection rule ID (e.g. 'WIN-PROT-BEHAVIORAL-MALWARE-EXEC-12B-T1059-001')
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It correctly identifies the tool as asynchronous and specifies the polling mechanism. It does not mention side effects or destructive actions, which is appropriate for a read-like query operation. The description adds value beyond the schema by explaining the async behavior.

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 that convey the essential operation and workflow. Every sentence adds value, with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose (async query start), its output (run ID), and the expected workflow (poll then retrieve). It references the relevant sibling tools for subsequent steps. Given the absence of an output schema and the tool's straightforward nature, the description is complete and informative.

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?

With 100% schema description coverage, the schema already describes each parameter's meaning and constraints. The description does not add additional parameter semantics or usage notes beyond what the schema provides. A baseline score of 3 is appropriate.

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 the action ('Start an async detections query run') and specifies the resource (detections query run). It distinguishes itself from sibling tools like sophos_get_detections_query_status and sophos_get_detections_query_results by indicating the workflow (start, then poll, then results).

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 provides explicit guidance on the usage flow: start, poll, retrieve. It does not explicitly state when to use this tool versus alternatives, but the context makes it clear that this is for initiating a new query, while siblings handle status and results. It lacks 'do not use when' statements but is generally clear.

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