Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-removeInvitation

Destructive

Removes a pending organization invitation by invitation ID, revoking access before the invitee joins. Use it to cancel or clean up invitations in Dokploy.

Instructions

POST /organization.removeInvitation

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": {
      "invitationId": "<invitationId>"
    },
    "name": "organization-removeInvitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
invitationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partially covered structurally. However, the description adds nothing: it does not say whether the invitation record is deleted or just expired, whether it is idempotent, what permissions are required, or what is returned on success. For a destructive mutation this is a thin disclosure even with annotations present.

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

Conciseness2/5

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

It is a single endpoint path with zero waste, but that brevity reflects under-specification rather than tight writing. Nothing is front-loaded because nothing beyond the route is conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A destructive, open-world mutation with no output schema and 0% parameter documentation needs the description to carry the burden, and this one provides none of the missing context. An agent cannot tell from the definition alone what the call destroys or what it returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required invitationId parameter, and the description supplies no meaning, format, or sourcing guidance (e.g., whether it is the invitation id versus token or email). The parameter name is suggestive but the definition does not compensate for the coverage gap.

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

Purpose2/5

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

The description is only the HTTP route "POST /organization.removeInvitation", which restates the tool name rather than stating in prose what the tool does. An agent can infer roughly that an invitation is revoked, but the definition itself adds no verb-object statement or scope beyond the identifier.

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, and no mention of how this differs from siblings such as organization.inviteMember, organization.allInvitations, or user.sendInvitation. The only cue is the name, leaving the agent to infer the conditions for calling it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools