Skip to main content
Glama

List organisation members

list_organisation_members
Read-only

Who has access to the organisation (the twin of ankra org members): each member's email, status, role and whether they are the current user, plus pending invites and Ankra's own service principals (the board agent, service tokens) marked as such. Use this for access reviews and for 'who is the admin here'. Read-only; invite_organisation_member, update_organisation_member_role and remove_organisation_member change membership and take the user_id shown here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that with 'Read-only'. Beyond the annotations it discloses non-obvious response content: pending invites are included and Ankra's own service principals are included but marked as such — exactly the kind of detail that prevents an agent from miscounting real users. No pagination or ordering behavior is mentioned.

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?

Front-loaded with the purpose and return contents, then routed to alternatives in the second half. It is dense but every clause carries information; the backticked CLI twin reference is the least essential element for an agent but does reinforce scope cheaply.

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 and no parameters, the description carries the full burden of describing return shape, and it does so field by field while noting the invite and service-principal edge cases. It is nearly complete; ordering and whether results are paginated or capped on large organisations are the only unaddressed details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline is 4. The description correctly implies no filtering and returns the whole organisation roster.

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?

The description states a specific verb+resource ('who has access to the organisation') and enumerates the returned fields: email, status, role, current-user flag, pending invites, and service principals. It distinguishes itself from the mutating siblings by naming them and calling this the read path, and the CLI twin reference anchors the scope.

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 triggering scenarios ('access reviews', 'who is the admin here') and names the three write alternatives (invite/update-role/remove) together with the condition that selects them and the user_id handoff. It stops just short of an explicit exclusion against the project-scoped sibling list_project_members, so not quite a 5.

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.