Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_technicians_list

Lists SuperOps.ai technicians sorted by name. Optionally narrow results by searching name or email substring to find specific agents.

Instructions

List technicians (agents) in SuperOps.ai, sorted by name. Optionally narrow the list with a search term, matched as a substring against both name and email. SuperOps does not expose an active/inactive flag, ticket counts or last-login times for technicians. Each technician's role comes back as {roleId, name} and their groups as an array of {groupId, name}; designation, businessFunction, team and reportingManager are null unless the tenant assigns them. listInfo.hasMore is true when a further page exists and null when it is not — it is never false, so page against totalCount. Use superops_custom_query for filters beyond a name search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based (default: 1, max: 2147483647)
searchNoSubstring matched against the technician's name or email address
pageSizeNoResults per page (default: 50, max: 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.2
    • removedInput schema / properties / activeOnly
      Removed value: -{
-  "default": true,
-  "description": "Show only active technicians (default: true)",
-  "type": "boolean"
-}
    • removedInput schema / properties / cursor
      Removed value: -{
-  "description": "Pagination cursor for fetching next page",
-  "type": "string"
-}
    • removedInput schema / properties / max
      Removed value: -{
-  "default": 50,
-  "description": "Maximum number of results (default: 50, 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"
+}
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Substring matched against the technician's name or email address",
+  "type": "string"
+}
    • removedInput schema / properties / teamId
      Removed value: -{
-  "description": "Filter by team/group ID",
-  "type": "string"
-}
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: it discloses the absence of active/inactive flags, ticket counts, and last-login data, and warns that listInfo.hasMore is null (never false) so callers must page against totalCount. These are non-obvious behavioral traits that cannot be inferred from the schema.

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?

Front-loads purpose and sorting, then layers search behavior, return shape, and pagination caveats. Dense but nearly every sentence carries distinct information; slightly long but justified by the missing output schema.

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

Completeness5/5

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

There is no output schema, so the description must carry return semantics, and it does: role as {roleId, name}, groups as {groupId, name}, and which fields are null unless assigned. Combined with pagination guidance, it is complete enough to call correctly.

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 coverage is 100% so the baseline is 3, but the description adds meaning by specifying that 'search' matches as a substring against both name and email, and that results are sorted by name. It adds value beyond the schema field 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?

States a specific verb and resource ('List technicians (agents) in SuperOps.ai, sorted by name') and clarifies the sort order. The scope (name/email substring search) distinguishes it from the plural sibling tools like superops_technicians_get and superops_technicians_groups.

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?

Explicitly routes overflow filtering to 'superops_custom_query' for filters beyond a name search, giving a clear when-to-use alternative. It doesn't address when to prefer superops_technicians_get for a single record, but that distinction is obvious from the name.

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