Skip to main content
Glama

List pending join requests

members_list_join_requests
Read-only

Pending join requests from invite links that require approval, with the role each would get.

GET /api/v1/members/join-requests

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. Manage members only when the user asks. Requires the user to be an owner or admin of the space; a write-level key can grant the member role, and admin needs a manage-level key (a 403 says which).

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

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the authorization model an agent actually needs: caller must be owner or admin, a write-level key can grant the member role, an admin requires a manage-level key, and a 403 indicates which. That is substantive behavioral context not present in the structured fields.

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?

The purpose is front-loaded in the first clause, followed by the endpoint and then the procedural guidance. Every sentence carries information; only the raw endpoint path is arguably filler, and it is short.

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?

For a single-parameter read-only list tool, the authorization and space-selection prerequisites are covered, and the phrase 'with the role each would get' hints at returned fields. With no output schema, however, the return shape (identities, timestamps, pagination) is left unspecified.

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?

Schema coverage is 100%, so the schema already documents targetSpaceId. The description still adds meaning beyond it by tying the parameter to a concrete workflow (call auth_verify first, ask the user when multiple spaces are returned) and by framing it as conditional on multi-space accounts.

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 names a specific resource and scope: pending join requests originating from invite links that require approval, and notes each carries the role it would grant. That is concrete enough to separate it from members_review_join_request or members_list_invitations, though the listing verb is only implied rather than stated.

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 explicit operating context: for multi-space accounts, call auth_verify, ask the user which space to use, then pass targetSpaceId; and 'Manage members only when the user asks.' It sets a clear boundary and prerequisite chain, but does not explicitly contrast with the sibling review tool.

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.