Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-allInvitations

Read-onlyIdempotent

Retrieve all pending and sent invitations for your Dokploy organization to review team access and manage membership requests.

Instructions

GET /organization.allInvitations

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "organization-allInvitations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered upstream. The description adds nothing beyond that: no statement of scope (single organization vs. global), pagination behavior, or permission requirements for an open-world read.

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 undeniably short with no wasted words, but that brevity is under-specification rather than concision: a bare route string is not a front-loaded explanation of purpose. A single clarifying clause about scope would have cost almost nothing and greatly improved usability.

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

Completeness2/5

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

The tool is simple (no parameters, no output schema), so requirements are modest, but the description still omits what the call returns and whether results span one organization or all of them. With no output schema, the description is the only place an agent could learn the shape and scope of the response, and it does not.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics for the description to explain, which sets the baseline at 4. Schema coverage is 100% and additionalProperties is false, leaving nothing ambiguous about inputs.

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 endpoint string "GET /organization.allInvitations", which restates the tool name rather than stating in plain language that this lists organization invitations. An agent can infer a read of the invitations collection, but there is no clarifying verb-plus-resource sentence, and no differentiation from siblings such as user-getInvitations or organization-all.

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 at all: nothing says whether this returns invitations across all organizations, whether it is the right call versus user-getInvitations for a single user, or what distinguishes it from organization-all. The only signal is the endpoint path itself.

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