Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_cases

List all security cases for a tenant, with filters by type, severity, status, assignee, and more. Supports pagination and sorting to quickly find specific investigations.

Instructions

List all cases/investigations for a tenant with rich filtering options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoExact match by case name
pageNoPage number (1-based)
sortNoSort column e.g. 'type:asc', 'severity:desc'
typeNoFilter by case type
statusNoFilter by case status. Self-managed cases support new/investigating/onHold/resolved; Sophos-managed also have actionRequired
verdictNoFilter by case verdict
assigneeNoFilter by assignee email, or 'Unassigned'
severityNoFilter by case severity
escalatedNoFilter by escalation status
page_sizeNoResults per page
tenant_idYesTenant UUID
managed_byNoFilter by who manages the case ('self' or 'sophos')
created_afterNoReturn cases created after this timestamp or duration
created_beforeNoReturn cases created before this timestamp or duration
overview_containsNoPartial match on case overview text
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It fails to mention pagination behavior, rate limits, or that this is a read-only operation. The phrase 'List all' might imply unbounded results without pagination context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence. It is efficient with no redundancy, though 'rich filtering options' is somewhat generic.

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?

With 15 parameters and no output schema, the description should provide more context on response format, pagination mechanics, and filter behavior. The minimal description leaves agents with incomplete understanding for effective invocation.

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 parameters are already documented. The description adds only the general phrase 'rich filtering options', which does not elaborate on specific filters or their usage 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?

The description clearly states the verb 'List' and resource 'cases/investigations' with scope 'for a tenant' and mentions 'rich filtering options'. It effectively distinguishes from sibling list tools by specifying the entity type.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like sophos_get_case or sophos_search_alerts. No context on prerequisites, exclusions, or preferred scenarios is given.

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