Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-setDefault

Idempotent

Set a specific organization as the default in Dokploy by passing its organizationId. Use it after choosing an organization to make it the active default for future actions.

Instructions

POST /organization.setDefault

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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, plus the title. The description adds nothing beyond the HTTP verb — it does not say the operation mutates the caller's default org, whether it displaces a previous default, whether elevated permissions are required, or whether the change is reversible. For a state-changing operation with only minimal annotation coverage, this leaves the behavioral burden almost entirely unmet.

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 text is short but only because it is under-specified, not because it is efficient. It offers no front-loaded statement of intent, just a bare route string that duplicates the tool name.

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?

With no output schema, no parameter documentation, and only two weak annotations, the description should explain the mutation's effect and result. It provides neither, so an agent would have to guess at semantics before calling.

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 parameter organizationId, so the description must compensate and does not — it never mentions the parameter or what identifier format is expected. The only meaning an agent gets is from the parameter name and the minLength constraint in the raw schema.

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 literally the route 'POST /organization.setDefault', which restates the tool name rather than explaining what setting a default organization means or what effect it has. An agent cannot tell from this whether it marks the org as default for the calling user, the workspace, or globally, nor how it differs from siblings like organization-active or organization-one.

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 preconditions, and no mention of alternatives such as organization-active or organization-update. The endpoint name implies switching a default, but nothing states when an agent should select this tool over the related organization tools.

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