Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_run_xdr_query

Read-only

Execute ad-hoc SQL queries against the Sophos data lake for threat hunting and investigation, returning a run ID to track progress and retrieve results.

Instructions

Run an ad-hoc XDR (Extended Detection and Response) SQL query against the Sophos data lake. Returns a run ID to poll for status and results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe SQL query string to execute (15–50000 characters)
to_dateNoEnd of the query time range. ISO 8601 timestamp or ISO 8601 duration.
from_dateNoStart of the query time range. ISO 8601 timestamp (e.g. '2024-01-01T00:00:00.000Z') or ISO 8601 duration (e.g. 'P7D')
tenant_idYesThe tenant ID to run the XDR query against
variablesNoJSON array of variable objects to substitute into the query template. Each object must have: name (string), dataType (double|integer|text|dateTime|boolean), value (string), and optionally pivotType (deviceId|deviceName|sophosPid|ipAddress|username|sha256|filePath|registryKey|url).
query_nameNoHuman-readable name for this query run (default: 'AdHoc')
endpoint_idsNoComma-separated list of endpoint UUIDs to scope the query. If omitted, the query runs against all eligible endpoints.
Behavior4/5

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

Annotations include readOnlyHint=true and destructiveHint=false. The description adds that the operation returns a run ID for polling, implying asynchronous behavior and persistence of data. It does not contradict annotations and provides extra context beyond structured fields.

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?

Single sentence, front-loaded with the core action and result. No wasted words; every part serves a purpose.

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

Completeness4/5

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

Despite 7 parameters and no output schema, the description covers the key points: it runs a query, is ad-hoc, returns a run ID for polling. The sibling tools handle status and results retrieval, so the description is sufficient for an agent to understand the interaction pattern.

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?

All parameters are described in the input schema (100% coverage). The description adds 'ad-hoc' context but does not expand on parameter usage beyond what the schema provides. With full schema coverage, a baseline 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?

Description uses a specific verb ('Run'), identifies the resource ('ad-hoc XDR SQL query against the Sophos data lake'), and notes the return value ('run ID to poll for status and results'). It distinguishes from siblings like 'sophos_run_saved_xdr_query' by specifying 'ad-hoc'.

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

Usage Guidelines3/5

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

The description implies usage when an ad-hoc query is needed, but does not explicitly state when to use versus alternatives (e.g., saved queries) or when not to use. Minimal guidance on context.

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