Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-all

Read-onlyIdempotent

Retrieve all organizations from a Dokploy instance to review available teams and manage access across projects and deployments.

Instructions

GET /organization.all

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-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, and openWorldHint=true; the description adds nothing beyond the word "GET", which merely repeats the read-only annotation. It says nothing about result size, ordering, pagination, or permissions required for a listing call.

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 comes from under-specification rather than efficiency. A bare endpoint path is not a usable front-loaded summary of the tool's behavior.

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?

With no output schema and eight sibling organization-listing/selection tools, the description needs to explain what is returned and how it differs from organization-active and organization-one. It provides none of that, leaving the agent unable to choose or call confidently.

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 no parameters and the schema is fully described (100% coverage), so there is no parameter semantics for the description to explain. Baseline 4 applies when no parameters exist.

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.all", which restates the tool name rather than explaining it. An agent can guess it lists organizations, but that inference comes from the name, not from the description, and nothing distinguishes it from siblings such as 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 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, or how it relates to the many other organization-* tools. No prerequisites, pagination expectations, or scope notes are given.

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