Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_get_siem_events

Retrieve Sophos security events from the last 24 hours for integration with external SIEM systems, with pagination support using cursors.

Instructions

Retrieve security events from the Sophos SIEM API for integration with external SIEM systems. Events are from the last 24 hours only. Use the cursor from the response (next_cursor) to paginate; check has_more to know if more pages exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return per request (min 200, max 1000, default 200)
cursorNoPagination cursor from a previous response (next_cursor field) to fetch the next batch of events
from_dateNoReturn events after this point in time. Must be a UTC Unix timestamp (seconds since epoch, e.g. '1700000000'). Must be within the last 24 hours.
tenant_idYesThe tenant ID to query SIEM events for
exclude_typesNoComma-separated list of event type strings to exclude from results (e.g. 'Event::Endpoint::UpdateSuccess,Event::Endpoint::Application::Detected')
Behavior4/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It clearly states the 24-hour time window and pagination mechanics, which are critical for correct use. It does not mention rate limits or authentication, but for a read-only get operation, transparency is adequate.

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?

Three concise sentences deliver purpose, time constraint, and pagination guidance. No fluff, all sentences earn their place. Front-loaded with the main action.

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?

Despite no output schema, the description covers essential context: time window, pagination fields (next_cursor, has_more), and the required tenant_id is implied. For a list/read tool, this is sufficiently complete for an agent to use correctly.

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. The description does not add new parameter semantics beyond what the schema already provides (e.g., cursor usage, from_date constraint). While it reinforces the time window, it does not enhance understanding of individual parameters.

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 retrieves security events from the Sophos SIEM API, specifying the resource and action. It distinguishes itself from sibling tools like sophos_get_alert by focusing on SIEM events, and includes key details like the 24-hour time window.

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 pagination instructions (cursor, has_more) and the time constraint (last 24 hours), guiding correct usage. However, it does not explicitly compare with alternatives or state when not to use this tool, which would elevate it to a 5.

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