Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List members

members_list
Read-onlyIdempotent

The workspace's Owner, members and guests with their level on each site (siteId → level), the sites you can give access to (manageSiteIds), and pending invites. Use a person's id as userId in members.set_levels or members.remove, and an invite's id in members.revoke_invite.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>"
    },
    "name": "members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds substantive behavioral context beyond that: the exact composition of the result set (owner, members, guests, per-site levels, manageable sites, pending invites) and the fact that ids from this response feed specific mutation tools. Pagination or result-size limits are not addressed.

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?

Two sentences, front-loaded with the return contents and then the follow-up usage. It is dense but every clause carries information; the only weakness is that the first sentence is a verbless fragment, which slightly slows parsing of what the tool actually does.

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?

With no output schema, the description carries the burden of describing returns, and it does so with reasonable specificity about the member categories and id semantics. What is missing is anything about pagination, ordering, or whether the list is complete for large workspaces — minor for a read-only listing tool.

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?

There is a single parameter, workspaceId, with 0% schema description coverage, and the description only alludes to it via 'The workspace's...'. The meaning is largely self-evident from the name, but the description does not confirm format or how to obtain a valid workspaceId, so it neither compensates for nor fully repeats 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 enumerates exactly what the tool returns: owner, members and guests with per-site levels, the sites the caller can grant access to, and pending invites. That is a clear resource statement, though it never uses a verb like 'list' and does not distinguish this from siblings such as site_people_list or shares_list.

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?

It gives strong downstream routing — use a person's id as userId in members.set_levels or members.remove, and an invite's id in members.revoke_invite — which is genuinely useful chaining guidance. However, it never says when to call this tool rather than a sibling roster tool, so the when-to-use side is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources