Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-create

Creates a new organization in your Dokploy instance using a required name and optional logo, so you can separate teams, projects, or resources.

Instructions

POST /organization.create

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

Input Schema

NameRequiredDescriptionDefault
logoNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and a title, so the description carries the full behavioral burden and provides none. It does not state required permissions, whether the new organization becomes the default, side effects on existing organizations, or what is returned; the bare POST token is the only hint that this is a mutation.

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 brevity here reflects under-specification rather than efficiency; a raw route string is not a front-loaded explanation of the tool's purpose.

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 tool with no output schema, no destructive/read-only annotations, and zero parameter documentation, the description should explain inputs and effects. It provides nothing beyond the endpoint path, leaving the definition inadequate.

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 the two parameters (name required with minLength 1, logo), and the description adds no meaning for either. An agent gets no guidance on name constraints, uniqueness, or logo format from any source.

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 string "POST /organization.create", which restates the tool name rather than describing the action. An agent can infer create-an-organization from the name plus POST, but the description itself adds no verb, scope, or distinction from siblings like organization-update or organization-delete.

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 versus alternatives such as organization-update or organization-setDefault, no prerequisites, and no exclusions. Everything must be inferred from the tool name.

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