Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_audit_events

Retrieve audit trail events for a Sophos Central tenant, filtering by date, category, user, and paginating to track admin actions, policy changes, and logins.

Instructions

List audit trail events for a Sophos Central tenant. Covers admin actions, policy changes, user logins, and configuration modifications. Supports filtering by date range, category, user, and cursor-based pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor returned by a previous response to fetch the next page of results
to_dateNoReturn events at or before this ISO 8601 UTC timestamp (e.g. '2024-01-31T23:59:59.999Z')
user_idNoFilter events to those performed by a specific user ID
categoryNoFilter by audit event category (e.g. 'policy', 'endpoint', 'iam', 'firewall')
from_dateNoReturn events at or after this ISO 8601 UTC timestamp (e.g. '2024-01-01T00:00:00.000Z')
page_sizeNoNumber of events per page (1–100, default 50)
tenant_idYesTenant UUID
max_resultsNoMaximum total number of audit events to return across all pages (used to cap large result sets)
Behavior3/5

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

With no annotations, the description carries full burden. It mentions filtering and pagination but does not disclose behavioral traits like read-only nature, rate limits, response size, or ordering. Adequate but not rich.

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 concise sentences, front-loaded with purpose and followed by key features. No wasted 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?

Covers purpose, event types, filtering, and pagination. Missing details on response structure or ordering, but given no output schema, it is reasonably complete for a list tool with 8 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds context by specifying 'audit trail events' and summarizing filtering options, improving clarity beyond the schema's individual parameter 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?

The description clearly states the tool lists audit trail events for a Sophos Central tenant, specifying event types and filtering capabilities. It is specific and distinguishes from sibling list tools.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., sophos_get_audit_event). The description implies usage for listing audit events but lacks exclusions or comparative 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