Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List team

list_team
Read-only

List workspace team members and their roles and status—active, suspended, or pending invitation. Filter by status or search text, and paginate with skip while hasMore is true.

Instructions

List the team - the people who manage this workspace - with their role and status (active, suspended, or a pending invitation). Not shoppers: those are records of the customer model. Read-only; filter by status or a search string; page on with skip while hasMore is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
searchNoMatch against email or name
statusNoFilter by membership status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.146.2
    • changedInput schema / properties / skip / minimum
      Previous value: --9007199254740991New value: +0
  2. Addedv0.73.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' in the description is largely redundant. What the description genuinely adds is the pagination contract (page on with skip while hasMore is true) and the concrete status value set including 'a pending invitation', which is not in the schema. With no output schema, more detail about the returned shape would have pushed this higher.

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?

Four short sentences, front-loaded with the core purpose and the disambiguation second. Every clause carries information: identity of the resource, exclusions, safety profile, filters, and pagination. No filler.

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?

For a four-parameter list tool with a cheap annotation set and no output schema, the definition covers purpose, exclusions, filtering, and pagination adequately. The only material omission is the semantics of limit (and its unusually wide numeric bound), which an agent would have to guess.

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 50%: search and status are documented, while skip and limit are not. The description partially compensates by explaining skip as pagination tied to hasMore and by spelling out the status values (active, suspended, pending invitation), but limit is left undefined in both places and 'a search string' adds little over the existing email/name match note. Baseline 3 is appropriate.

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 the team') and immediately defines the resource as 'the people who manage this workspace', with the fields returned (role, status). It also pre-empts confusion with a near-sibling concept: 'Not shoppers: those are records of the customer model.' An agent can tell this apart from list_customers without opening any schema.

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?

Gives clear conditions: read-only use, filter by status or search string, and continue paging with skip while hasMore is true. It also names a class of thing this is NOT (shoppers / customer records), which is real exclusion guidance. It does not name a specific sibling tool to use instead for customer records, which keeps it from a 5.

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