Skip to main content
Glama

List pending email invitations

members_list_invitations
Read-only

Pending email invitations for this space.

GET /api/v1/members/invitations

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

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

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint true, destructiveHint false), so the bar is lower, and the description adds real context beyond them: owner/admin permission requirement, key-level requirements, and the fact that a 403 both signals and identifies the missing level. It omits pagination or result-size behavior, which would be the remaining useful detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening line is front-loaded and efficient, but the raw endpoint string (GET /api/v1/members/invitations) adds no decision value for an agent. The permission sentence is dense and slightly ambiguous ("a write-level key can grant the member role" inside a read-only listing tool), which costs clarity.

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 one-optional-parameter read tool with no output schema, the definition covers the decisions that matter: space selection, auth, and permission level. It does not describe what a pending invitation entry contains, which is the only meaningful gap given no output schema exists.

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?

There is a single optional parameter with 100% schema description coverage that already explains auth_verify and space selection. The description restates that guidance in prose without adding new syntax, defaults, or constraints, so it neither compensates for nor exceeds the schema.

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 the specific resource ("Pending email invitations for this space") and thereby distinguishes itself from siblings like members_list_invite_links and members_list_join_requests, which cover different artifact types. The verb is only implied by the tool name rather than stated, which keeps it just short of a 5.

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 a concrete precondition flow (call auth_verify for multi-space accounts, ask the user which space, pass targetSpaceId) and a gating rule ("Manage members only when the user asks"). It stops short of explicitly saying when to prefer this over invite-links or join-requests listings, so no exclusion guidance is present.

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.