Skip to main content
Glama

Accept a workspace invitation

accept_workspace_invitation
Idempotent

Accepts an invitation addressed to the connected account and grants membership in the inviting workspace.

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": {
      "invitation_id": "<invitation_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "accept_workspace_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
invitation_idYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and idempotency are covered structurally. The description adds real behavioral value by explaining the side effect (membership is granted) and the account binding, but it omits failure modes such as expired/revoked invitations or invitations addressed to a different account.

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

Conciseness5/5

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

A single front-loaded sentence with the action first and the consequence second; nothing is redundant or padded.

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 two-parameter mutation with no output schema, the definition covers the core effect but leaves gaps an agent would care about: what is returned on success (membership details?), whether the call fails on an already-accepted invitation, and how idempotency interacts with a retried acceptance.

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?

Schema description coverage is 50%: idempotency_key is well documented in the schema itself, while invitation_id has only length bounds and no description. The description implies invitation_id is an invitation addressed to the connected account, which adds a little meaning, but it does not say how the ID is obtained or what form it takes.

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 ('Accepts') and resource ('invitation') plus the effect ('grants membership in the inviting workspace'), which clearly separates it from invite_workspace_member or list_workspaces. It stops short of naming a sibling or stating the inverse operation, but the action 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 Guidelines2/5

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

There is no when-to-use guidance: no prerequisites (e.g. an invitation must already exist and be pending), no note on where invitation_id comes from, and no mention of what to do with an expired or already-accepted invitation. The only usage signal is the implicit 'addressed to the connected account' constraint.

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.

Resources