Skip to main content
Glama
Heliyos MCP server

Heliyos MCP server

Official
by heliyos-ai

List team members

heliyos_team_members_list
Read-onlyIdempotent

List workspace members and pending invitations with their roles and statuses, and filter results by role or by name/email text.

Instructions

Lists the workspace's people: joined members and pending invitations, each with its membership_id, email, name, role (OWNER, ADMIN, MEMBER) and status (active, invited, declined or revoked). Filter by role or by text in the name or email. Returns structuredContent {members:[{membership_id, email, name, role, status}], total, next_cursor}.

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": "heliyos_team_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoOnly members with this role.
limitNoMembers per page, 1 to 100. Default 20.
cursorNonext_cursor from the previous page, with the same limit. Omit for the first page.
searchNoPlain words matched against names and email addresses. Symbols such as + ( ) [ ] * ? can cause an error.
response_formatNo"concise" (default) returns one row per person; "detailed" returns user ids and invitation dates too.concise

Output Schema

NameRequiredDescriptionDefault
totalNo
membersYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/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 safety is covered. The description adds real value beyond them: it discloses that pending invitations (not just active members) are included, enumerates the status values, and surfaces cursor-based pagination via next_cursor and total. It omits whether the caller's permissions limit what is visible, which is the main remaining gap.

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 sentences, front-loaded with what the tool returns, then filtering, then response shape — every sentence carries information. The final sentence restating the structuredContent envelope partially duplicates the existing output schema, which is the only mild redundancy.

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?

For a paginated read tool, the definition covers scope (members plus invitations), filterability, the meaning of each returned field, and pagination tokens; annotations and the output schema carry the safety and shape details. An agent has everything needed to call it correctly without further inspection.

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 role, limit, cursor, search and response_format. The description restates the role and search filters at a high level without adding format or edge cases (the search-symbol caveat and the 1–100 limit live only in the schema), so it does not meaningfully exceed the baseline.

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?

"Lists the workspace's people: joined members and pending invitations" gives a specific verb, resource, and scope, and enumerates the returned fields (membership_id, email, name, role, status). Nothing overlaps with the sibling mutators (team_members_invite, team_members_remove, team_members_change_role), so an agent can pick this tool unambiguously.

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 states the tool filters by role or by text in name/email, which implies the use case, but there is no explicit "use this when…" framing, no prerequisite (e.g., admin permission), and no mention of when to prefer another listing tool. Usage is inferable rather than stated.

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