Skip to main content
Glama

Approve or reject a join request

members_review_join_request
Destructive

Approve or reject a pending join request.

POST /api/v1/members/join-requests/{joinRequestId}/review

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). Approve or reject only when the user explicitly decides.

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": {
      "joinRequestId": "<joinRequestId>",
      "decision": "<decision>"
    },
    "name": "members_review_join_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
joinRequestIdYes
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.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely new behavioral context: required owner/admin role, key-level differences (write-level for member role, manage-level for admin), and that a 403 reports which level is missing. It does not say what state the request is left in after a decision or what the response contains, so it is strong but not exhaustive beyond the annotations.

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-loads the action, then the endpoint, then prerequisites and guardrails — a sensible order with no filler. The middle block is a dense run-on sentence mixing key levels, 403 semantics, and consent rules, which costs some readability but every clause carries information.

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?

For a destructive 3-parameter mutation with no output schema, the definition covers authorization, space selection, and user-consent gating. The main omission is the outcome: it never states what approving does (e.g., grants member role) or what is returned, though the key-level sentence hints at the role-granting effect.

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?

With only 33% schema coverage, the description carries real weight: it explains the multi-space workflow for targetSpaceId (verify then ask the user), identifies joinRequestId via the endpoint template, and enumerates the two decision values in prose. It still does not clarify whether targetSpaceId is required when the account has a single space, which is the one ambiguity left.

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?

States a specific verb pair and resource ('Approve or reject a pending join request') and reinforces it with the exact endpoint path POST /api/v1/members/join-requests/{joinRequestId}/review. The action is unambiguous, though it never names the sibling list tool (members_list_join_requests) to draw the read-vs-review boundary explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions and exclusions: call auth_verify and ask the user which space when multiple exist, pass targetSpaceId, 'Manage members only when the user asks', and 'Approve or reject only when the user explicitly decides'. Both the when and the when-not are stated, which is exactly the guidance an agent needs before a destructive member action.

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.