FeatureOS

List team members

list_team_members

Read-only

List team members in the organization.

Each member is {id, user: {name, email}, role, admin}, where id is the membership id (not the user id). To assign a member to a feature request, pass their user.email to assign_feature_request — it keys on email, not id. Use the role filter ('admin', 'member', 'csm') to narrow the list.

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_members"
  }
}

Input Schema

Name	Required	Description	Default
`role`	No	Filter by role: 'admin', 'member', or 'csm'.
`sort`	No	Time order: 'latest_created_at', 'oldest_created_at', 'latest_updated_at', or 'oldest_updated_at'. Omit for the default order.

Output Schema

Name	Required	Description	Default
`page`	No
`members`	No
`has_more`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-schema context: the id field is the membership id rather than the user id, and the record shape. It says nothing about pagination, result size limits, or default sort behavior, so it sits at an adequate 3.

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 short sentences, front-loaded with the resource scope, then the return shape, then the cross-tool usage note. Every sentence carries information an agent needs; there is 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 two-parameter, zero-required read tool with an output schema, the description covers scope, return shape, and the key cross-tool handoff. The only gap is the undocumented `sort` behavior (what the default order is), which is minor given full schema coverage.

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 both parameters are already documented in the schema, making 3 the baseline. The description restates the role filter values and adds no new semantics for `role`, and it is completely silent on the `sort` parameter, adding no meaning beyond the schema.

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 opens with a specific verb and resource ('List team members in the organization'), which is unambiguous. It does not explicitly distinguish itself from the sibling get_team_member (single fetch) or list_customers, leaving that differentiation implicit, so it falls short of a 5.

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?

It gives concrete downstream guidance: pass a member's user.email to assign_feature_request because that tool keys on email, not membership id. It also explains when to use the role filter. It lacks explicit exclusions (e.g., when to use get_team_member instead), so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FeatureOS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.