Skip to main content
Glama
rijul170

Sophos Central MCP Server

by rijul170

sophos_list_mobile_devices

Read-only

List mobile devices enrolled in a Sophos tenant, with filters for platform, compliance, ownership, and date ranges. Returns paginated results.

Instructions

List mobile devices enrolled in Sophos Mobile for a tenant. Supports filtering by platform, management type, compliance status, health state, ownership, device groups, and date ranges. Returns paginated results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (starting at 1)
sortNoSort expression (e.g. 'name:asc')
fieldsNoComma-separated list of fields for a partial response
searchNoFree-text search term
platformNoFilter by device platform / OS
compliantNoFilter by compliance status (true=compliant, false=non-compliant)
page_sizeNoNumber of results per page
tenant_idYesTenant UUID
page_totalNoWhether to include total page count in the response
health_stateNoFilter by health status
created_afterNoISO 8601 datetime — return devices created after this time
managed_stateNoFilter by management status
created_beforeNoISO 8601 datetime — return devices created before this time
ownership_typeNoFilter by device owner type
last_seen_afterNoISO 8601 datetime — return devices last seen after this time
management_typeNoFilter by management type (e.g. mdm, mam)
device_group_idsNoComma-separated device group UUIDs to filter by
last_seen_beforeNoISO 8601 datetime — return devices last seen before this time
violation_severityNoFilter by compliance violation severity
Behavior3/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds pagination and filter capabilities, which are useful but not extensive. No contradictions with annotations.

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?

Two sentences front-load the core action and then list filters and pagination. Every word serves a purpose, no filler. Highly concise for a tool with 19 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 19 parameters and no output schema, the description covers the main action and filters but omits details like required tenant_id, response structure beyond pagination, rate limits, or authentication context. Adequate but not thorough.

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 the schema already describes all 19 parameters. The description summarizes filter types but does not add meaning beyond the schema's individual parameter descriptions. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists mobile devices and mentions filtering options. However, it does not explicitly differentiate from sibling tools like sophos_list_mobile_device_policies or sophos_get_mobile_device, leaving the agent to infer its unique role.

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. It does not specify any prerequisites, exclusions, or comparative context with sibling tools that also list resources (e.g., sophos_list_endpoints, sophos_list_alerts).

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