Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_clients_list

List SuperOps.ai clients with paginated results, filter by stage or status, and combine both filters to narrow matching accounts.

Instructions

List clients (accounts) in SuperOps.ai. Results are paginated with page/pageSize. Supplying both stage and status narrows to clients matching both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based (default: 1, max: 2147483647)
stageNoFilter by stage: Active, Inactive, or Prospect. Combined with status if both are given. Your tenant may rename or extend this list.
statusNoFilter by status. Status is a sub-state of stage: Paid and Unpaid belong to stage Active; New, Negotiation, Won and Lost belong to stage Prospect. Stage Inactive has no statuses. Pairing a status with a stage it does not belong to matches nothing. Your tenant may rename or extend this list.
pageSizeNoResults per page (default: 50, max: 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.2
    • 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"
+}
    • changedInput schema / properties / stage / description
      Previous value: -"Filter by stage: Lead, Prospect, Customer, or Churned"New value: +"Filter by stage: Active, Inactive, or Prospect. Combined with status if both are given. Your tenant may rename or extend this list."
    • removedInput schema / properties / stage / enum
      Removed value: -[
-  "Lead",
-  "Prospect",
-  "Customer",
-  "Churned"
-]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: Active, Inactive, or Archived"New value: +"Filter by status. Status is a sub-state of stage: Paid and Unpaid belong to stage Active; New, Negotiation, Won and Lost belong to stage Prospect. Stage Inactive has no statuses. Pairing a status with a stage it does not belong to matches nothing. Your tenant may rename or extend this list."
    • removedInput schema / properties / status / enum
      Removed value: -[
-  "Active",
-  "Inactive",
-  "Archived"
-]
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose pagination behavior and the stage/status AND semantics, which is genuinely useful, but says nothing about read-only nature, permission requirements, rate limits, or whether tenant-renamed stages/statuses affect filtering outcomes beyond the schema's own note.

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?

Three short sentences with no filler, and the core action is front-loaded. Slightly more could be trimmed since the pagination and filter sentences largely duplicate schema content, but structure is clean.

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?

With no output schema and no annotations, the description should do more work: it does not describe the shape of returned client records or whether pagination metadata (total counts) is returned. Pagination and filtering are covered, but an agent calling it blind still lacks return-value expectations.

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 schema already documents page, pageSize, stage, and status in detail. The description's restatement that supplying both stage and status narrows results adds only marginal value over the schema's own 'Combined with status if both are given' note. Baseline 3 applies.

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?

States a specific verb and resource: 'List clients (accounts) in SuperOps.ai', clarifying that 'clients' and 'accounts' are the same entity. However, it never distinguishes itself from the sibling superops_clients_search, leaving the agent to infer which list-style tool to pick.

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

Usage Guidelines3/5

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

Provides implicit usage context via pagination and the stage/status combination rule, but offers no when-to-use guidance or explicit alternative (e.g., use search when you need text matching). The agent must infer the boundary with superops_clients_search on its own.

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