Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-one

Read-onlyIdempotent

Retrieves details for a specific Dokploy organization by its organization ID, enabling inspection of organization settings and metadata.

Instructions

GET /organization.one

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

Input Schema

NameRequiredDescriptionDefault
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered elsewhere. The description adds nothing beyond the verb: no mention of error behavior for unknown IDs, authentication requirements, or what 'one' returns.

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?

Extremely short, but brevity here is under-specification rather than economy. The single route string carries no actionable instruction and is not front-loaded around intent.

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, one undocumented parameter, and no annotations explaining the 'one' semantics, the description leaves an agent with almost nothing to call the tool correctly beyond the route itself.

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 coverage is 0% for the single required parameter organizationId, and the description says nothing about it — no format, source of the ID, or whether it is a slug vs numeric identifier. The description completely fails to compensate for the schema gap.

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 just the HTTP route 'GET /organization.one', which restates the tool name rather than defining it. An agent can infer it fetches a single organization by ID, but nothing states that explicitly or distinguishes it from the 'organization-all' sibling.

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?

No guidance on when to use this versus organization-all, organization-active, or other single-resource siblings. The agent must guess that this is the by-ID lookup.

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