Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_assets_list

List and filter SuperOps RMM assets by status, platform, or client ID, with paging, to find the endpoints you need to manage.

Instructions

List assets (endpoints) in SuperOps.ai RMM. Supply any combination of status, platform and clientId; several filters are combined with AND. listInfo.hasMore is true when a further page exists and null (never false) when it does not, so treat null as the end or page against totalCount.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based (default: 1, max: 2147483647)
statusNoFilter by asset status, matched whole and case-insensitively. Observed values are "ONLINE" and "OFFLINE"; SuperOps validates the value at runtime, so a status this tenant uses but the list omits still works.
clientIdNoFilter by client account ID — the `accountId` inside an asset's `client` object, as returned by superops_clients_list.
pageSizeNoResults per page (default: 50, max: 100)
platformNoSubstring of the platform string, matched case-insensitively. SuperOps stores a full OS name ("Microsoft Windows 10 Pro", "darwin"), so pass a fragment such as "Windows" or "darwin" rather than a whole name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.0.2
    • changedInput schema / properties / clientId / description
      Previous value: -"Filter by client account ID"New value: +"Filter by client account ID — the `accountId` inside an asset's `client` object, as returned by superops_clients_list."
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Pagination cursor for fetching next page",
-  "type": "string"
-}
    • removedInput schema / properties / max
      Removed value: -{
-  "default": 100,
-  "description": "Maximum number of results (default: 100, max: 500)",
-  "type": "number"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, 1-based (default: 1, max: 2147483647)",
+  "type": "number"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "default": 50,
+  "description": "Results per page (default: 50, max: 100)",
+  "type": "number"
+}
    • changedInput schema / properties / platform / description
      Previous value: -"Filter by platform: Windows, macOS, or Linux"New value: +"Substring of the platform string, matched case-insensitively. SuperOps stores a full OS name (\"Microsoft Windows 10 Pro\", \"darwin\"), so pass a fragment such as \"Windows\" or \"darwin\" rather than a whole name."
    • removedInput schema / properties / platform / enum
      Removed value: -[
-  "Windows",
-  "macOS",
-  "Linux"
-]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: Online, Offline, or Maintenance"New value: +"Filter by asset status, matched whole and case-insensitively. Observed values are \"ONLINE\" and \"OFFLINE\"; SuperOps validates the value at runtime, so a status this tenant uses but the list omits still works."
    • removedInput schema / properties / status / enum
      Removed value: -[
-  "Online",
-  "Offline",
-  "Maintenance"
-]
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the non-obvious AND-combination semantics of the filters and the unusual pagination contract where listInfo.hasMore is null (never false) at the end. It omits permission/auth or rate-limit context, but for a read-only list tool the pagination quirk is the highest-value behavioral detail.

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?

Three sentences, zero padding, and the core purpose is front-loaded before the filtering and pagination guidance. Every sentence carries information an agent needs.

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

Completeness4/5

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

No output schema exists, so the description reasonably steps in to explain the pagination return signal (listInfo.hasMore). Combined with the high schema coverage for parameters, an agent has enough to call it correctly, though the overall response shape is only partially sketched.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and the description earns above it by adding the filter-combination logic (multiple filters are ANDed) that the schema does not state. It doesn't add per-parameter format detail, but that is already covered by the schema.

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?

States a specific verb and resource ('List assets (endpoints)') with the product context ('in SuperOps.ai RMM'). The parenthetical clarifies that 'assets' means endpoints, which distinguishes it from siblings like superops_assets_software and superops_assets_patches.

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

Usage Guidelines4/5

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

Tells the agent how to invoke it ('Supply any combination of status, platform and clientId; several filters are combined with AND'), which is clear operational context. However, it never names when to prefer this over sibling tools such as superops_assets_get or the software/patches variants.

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