Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_mobile_actions

List MDM actions (sync, scan, lock, wipe, etc.) for a tenant. Filter by type, state, endpoint IDs, and date ranges to manage mobile device actions.

Instructions

List MDM actions (sync, scan, lock, wipe, etc.) for a tenant with filtering by type, state, endpoint IDs, and date ranges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
page_sizeNoResults per page
tenant_idYesTenant UUID
action_typeNoFilter by action type (e.g. sync, scan, lock, wipe, unenroll, sendMessage, locate, getLogs)
action_errorNoFilter by action error code
action_stateNoFilter by action status (e.g. pending, completed, failed)
endpoint_idsNoComma-separated endpoint UUIDs to filter by
executed_afterNoISO 8601 datetime — actions executed after this time
executed_beforeNoISO 8601 datetime — actions executed before this time
scheduled_afterNoISO 8601 datetime — actions scheduled after this time
scheduled_beforeNoISO 8601 datetime — actions scheduled before this time
Behavior2/5

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

No annotations are provided, and the description does not mention behavioral traits like pagination, rate limits, read-only nature, or data freshness. The burden falls on the description, but it only states the listing function.

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?

The description is a single concise sentence (18 words) with key information front-loaded ('List MDM actions'). Every word adds value; no redundant or vague phrasing.

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?

Given 11 parameters, no output schema, and no annotations, the description lacks details on return format, pagination behavior, or constraints. It is insufficient for an agent to fully understand the tool's use without relying on schema alone.

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 baseline is 3. The description groups filter types (type, state, endpoint IDs, date ranges) but adds minimal semantic value 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 MDM actions with examples (sync, scan, lock, wipe) and specifies filtering capabilities. It distinguishes from sibling tools like sophos_get_mobile_action (single action) and specific action tools by its listing focus.

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 such as sophos_get_mobile_action or other list tools. It lacks explicit usage context, prerequisites, or exclusions.

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