Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-inviteMember

Idempotent

Invite a user to a Dokploy organization with a specified email and role to grant appropriate access to deployments and infrastructure.

Instructions

POST /organization.inviteMember

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": {
      "email": "<email>",
      "role": "<role>"
    },
    "name": "organization-inviteMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, lowering the disclosure bar, but the description adds no behavioral context at all. It does not say whether an invitation email is dispatched, whether the invitee must already exist, what happens on a duplicate invite, or what authorization is required for a mutation that grants access.

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 short, but that brevity reflects under-specification rather than economy — the single route string carries no informational payload. There is no front-loaded purpose statement or structure an agent can act on.

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?

For a mutation that grants organizational access, with no output schema and undocumented parameters, the definition is essentially empty. An agent cannot determine required permissions, side effects, role semantics, or the result of the call.

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

Parameters1/5

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

Schema description coverage is 0% for two required parameters (email, role), and the description supplies no meaning for either. Critically, it does not enumerate or constrain valid role values, which is the highest-value piece of information missing here.

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.inviteMember", which restates the tool name in URL form rather than stating in prose that it invites a member to an organization. An agent can infer the intent from the name, but the description itself adds no verb-and-resource statement, no scope, and no differentiation from siblings such as organization-updateMemberRole or organization-allInvitations.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to, prerequisites (e.g., admin rights, existing membership), or which sibling to prefer for related operations. The route string implies nothing about selection between alternatives.

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