Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_get_detection_counts

Retrieve detection counts grouped by severity and type over a specified time range, with hourly or daily bucket resolution. Filter by tenant, rule, severity, type, and other criteria.

Instructions

Get detection counts grouped by severity and type over a time range. Returns per-hour or per-day buckets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoComma-separated detection types (e.g. 'threat,process,vulnerability')
sourceNoSensor source to filter on (e.g. 'Sophos')
to_dateNoEnd of time range (ISO 8601)
severityNoComma-separated severity scores to filter on
usernameNoFilter by username
from_dateNoStart of time range (ISO 8601)
tenant_idYesTenant UUID
resolutionNoBucket resolution: 'hour' or 'day'
entity_typeNoFilter by entity type (e.g. 'computer', 'server')
detection_ruleNoFilter by a specific detection rule ID
show_suppressedNoIf true, include suppressed detections
device_name_containsNoFilter by partial device hostname
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. It only mentions output format (per-hour/per-day buckets) without addressing side effects, authentication, rate limits, or other behaviors. For a read operation, the description is minimally transparent.

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 wasted words, directly conveys core functionality. Front-loaded with key action and output.

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?

Despite having 12 parameters, description ignores filters like source, username, entity_type, detection_rule, show_suppressed, device_name_contains. While output is described, the extensive filtering capability is omitted, making it incomplete for an agent to understand all functionality.

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 is 3. Description does not add parameter-specific details beyond the schema; it only mentions grouping by severity and type, which corresponds to parameters already described in the 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 clearly states the verb (Get), resource (detection counts), grouping (by severity and type), time range, and bucket resolution. It distinguishes from sibling tools that retrieve individual detections or query results.

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?

Description implies the tool is for aggregated counts over time, but does not explicitly specify when to use it versus alternatives like sophos_get_detections_query_results. No exclusion criteria or context for sibling tools.

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