Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-sendInvitation

Idempotent

Sends a user invitation using the specified invitation and notification IDs to notify the recipient.

Instructions

POST /user.sendInvitation

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>",
      "notificationId": "<notificationId>"
    },
    "name": "user-sendInvitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
invitationIdYes
notificationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the side-effect profile is partly covered; the description adds nothing about what the invitation does, whether it sends email, requires auth, or fails on duplicates. With a mutation-style tool and zero added context, this is a significant gap rather than a contradiction.

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?

The single fragment is short but not informative; brevity here reflects under-specification rather than economy. There is no front-loaded statement of intent or effect.

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 two-required-parameter action with no output schema and no parameter documentation, the description supplies nothing an agent needs in order to call it correctly. It is effectively an empty definition.

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?

Both required parameters (invitationId, notificationId) have 0% schema description coverage, and the description does not explain what either identifier refers to or where to obtain them. The description provides no compensating meaning whatsoever for the undocumented parameters.

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 raw route string "POST /user.sendInvitation", which restates the tool name rather than explaining what sending an invitation does, to whom, or what effect it has. An agent can infer a write-ish action from the name, but nothing beyond the identifier is added.

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 user-getInvitations or organization-removeInvitation. The endpoint string gives no selection criterion at all.

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