Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_create_case

Create a new investigation case to document and track security incidents, threats, hunts, or vulnerabilities in your organization.

Instructions

Create a new investigation case.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCase name
typeNoCase type (e.g. 'threat', 'hunt', 'incident')
statusNoInitial case status
assigneeNoAssignee email address
overviewNoCase overview/description text
severityNoCase severity (e.g. 'notSet', 'high', 'critical')
tenant_idYesTenant UUID
managed_byNoWho manages the case ('self' or 'sophos')
other_detection_idsNoAdditional detection IDs to associate with the case
initial_detection_idNoID of the initial detection that triggered this case
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description's 'Create' is consistent but adds no behavioral details beyond the annotations. No mention of side effects, auth needs, or other traits.

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

Conciseness3/5

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

The description is very concise (5 words) but lacks structure for a tool with 10 parameters. It is front-loaded with the verb, but too terse to be fully informative.

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 10 parameters, no output schema, and no behavioral context, the description is incomplete. It does not explain what happens upon creation, return values, or prerequisites.

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 description coverage is 100%, so the schema fully documents parameters. The description adds no additional meaning beyond the schema, resulting in baseline score of 3.

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 'Create a new investigation case' uses a specific verb and resource, clearly distinguishing it from sibling tools like sophos_list_cases, sophos_get_case, and sophos_update_case.

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 (e.g., sophos_update_case for modifying cases, sophos_get_case for reading), nor any prerequisites or 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