Skip to main content
Glama
Sign In
Sophos Central MCP Server

Sophos Central MCP Server

by rijul170
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sophos_manage_mailbox_dl_owners

Add or remove distribution list owners for a mailbox. Use tenant UUID and mailbox UUID to specify the mailbox and provide email addresses to add or remove.

Instructions

Add or remove distribution list owners for a mailbox.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenant_id": "<tenant_id>",
      "mailbox_id": "<mailbox_id>"
    },
    "name": "sophos_manage_mailbox_dl_owners"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNoEmail addresses of DL owners to add
removeNoEmail addresses of DL owners to remove
tenant_idYesTenant UUID
mailbox_idYesMailbox UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive nature, but the description adds no additional behavioral context such as permissions needed or side effects beyond the stated action.

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, efficient sentence that is front-loaded and concise, though it could be expanded with structured usage notes.

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?

Lacking an output schema and additional context such as error handling or return values, the description is insufficient for a mutation tool, especially given similar sibling tools.

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?

All parameters are fully described in the schema (100% coverage), so the description adds no extra meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 specifies adding or removing distribution list owners for a mailbox, using specific verbs and resource, which distinguishes it from sibling tools like sophos_manage_mailbox_aliases and sophos_manage_mailbox_delegates.

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, nor does it mention prerequisites or context for its use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools