Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_get_detections_group_results

Retrieve grouped detection results from a completed query, providing counts, detection rules, MITRE ATT&CK tags, and device information for each group of similar detections.

Instructions

Get results of a completed detection-groups query. Each item represents a group of similar detections with a count, detection rule, MITRE ATT&CK tags, and device info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default 1)
run_idYesDetection-groups query run ID
page_sizeNoNumber of results per page (default 50, max 2000)
tenant_idYesTenant UUID
Behavior3/5

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

No annotations provided. Description indicates read-only operation on completed queries but lacks details on pagination behavior, prerequisites (run_id from a started query), or error conditions.

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, first states purpose, second details result structure. No redundancy or unnecessary words.

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?

Explains result item fields, compensating for lack of output schema. Could clarify that run_id comes from a prior start query, but overall adequate for a simple retrieval tool.

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% (all parameters described). Description adds no additional parameter meaning beyond schema descriptions.

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 clearly states it retrieves results of a completed detection-groups query and describes the item content (count, rule, MITRE tags, device info), distinguishing it from siblings like get_detections_group_query_status.

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?

Implied usage for completed queries only, but no explicit when to use or alternatives. Siblings exist (start_detections_group_query, get_detections_group_query_status) but not mentioned.

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