Skip to main content
Glama

Respond to invitation

respond_to_invitation
Destructive

Accepts one invitation (accept with its invitation_id) or declines all of them and creates the user's own organization (decline_all). Irreversible: the account can never switch organizations afterwards. Only call this after the user explicitly chose an option in this conversation.

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": {
      "action": "<action>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "respond_to_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesaccept: join the organization of `invitation_id`. decline_all: revoke all invitations and create the user's own organization.
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
invitation_idNoRequired for accept: the `id` from list_invitations.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Adds real value beyond annotations with the irreversibility warning that the account can never switch organizations afterwards, which is not obvious from destructiveHint alone. With destructiveHint and idempotentHint=false already supplied, however, it does not add per-mode effects on failure or whether a declined invitation can be reinstated.

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?

Two sentences, both load-bearing: the first defines the modes, the second carries the irreversibility and consent constraints. The operative risk warning is front-loaded after the capability statement with no filler.

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, non-idempotent single-shot decision tool, the description covers the modes, the risk, and the consent requirement, while the schema carries the conversation_id and analytics-parameter mechanics. What it omits is minor: which response or state results from each branch, though for a terminal choice this is largely self-evident.

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 coverage is 100%, so action, invitation_id, context, llm_model and conversation_id are already documented in the schema. The description only restates the accept/decline_all split and the conditional requirement of invitation_id, adding little beyond the schema's own enum descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific verb (accepts/declines) plus the two mutually exclusive modes with their action keys, so an agent can map intent directly onto the enum. It is clearly distinct from list_invitations, which only surfaces the invitations this tool consumes.

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?

Gives an explicit precondition: only call after the user has explicitly chosen an option in this conversation, which effectively forbids autonomous invocation. It does not name alternative tools (e.g. list_invitations to find the id), leaving that inference to the agent.

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.