Skip to main content
Glama

List the space's app users

app_users_list
Read-only

App users, newest first.

GET /api/v1/app-users

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId.

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

Input Schema

NameRequiredDescriptionDefault
appIdNo
emailNo
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 result ordering (newest first) and the underlying endpoint, but says nothing about pagination, result caps, or default page size for a list operation, which is the main behavioural unknown here.

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 short lines, front-loaded with the resource and ordering, then the endpoint, then the multi-space procedure. The raw endpoint path adds little for an agent but costs almost nothing; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and three loosely documented parameters, the agent still does not know what a listed app user looks like, how many are returned, or how appId/email filters behave. The multi-space prerequisite is handled well, which keeps this at an adequate rather than incomplete level.

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

Parameters2/5

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

Schema coverage is only 33%, and the description only restates the targetSpaceId procedure already spelled out in the schema. The appId and email parameters are not explained in either place, so the description fails to compensate for the low coverage on a filtering tool where their semantics matter.

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?

"App users, newest first" identifies the resource and result ordering, and the GET endpoint confirms it is a read. The verb "list" is implied rather than stated, and the read/write split from siblings such as app_users_delete or app_users_enable is left implicit, but the purpose is unambiguous.

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 a concrete procedural rule for multi-space accounts (call auth_verify, ask the user, pass targetSpaceId), which is genuinely useful. It never says when to use this tool versus alternatives like members_list or the activity list tools, and filtering behaviour (by appId or email) is left unexplained.

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.