Skip to main content
Glama
MCP Dokploy Online
by igoruam

compose-refreshToken

Idempotent

Regenerate the access token for a specific Dokploy compose service using its compose ID. Use it to rotate or replace an existing token.

Instructions

POST /compose.refreshToken

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": {
      "composeId": "<composeId>"
    },
    "name": "compose-refreshToken"
  }
}

Input Schema

NameRequiredDescriptionDefault
composeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations supply openWorldHint=true and idempotentHint=true, and the description adds only the POST method, implying a state-changing call. It says nothing about authorization requirements, whether the previous token is invalidated (a critical consequence for a refresh operation), or token lifetime, so the most important behavioral facts are absent.

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?

There is no wasted wording, but that is because there is essentially no content; a bare route string is under-specification rather than conciseness and does not front-load any actionable information.

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 credential-issuing operation with no output schema, the agent needs to know what comes back (a token string?), how it is delivered, and what old credentials become invalid. None of this is present, so the definition is insufficient to invoke the tool correctly.

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 composeId, so the description carries the full burden and adds nothing — no hint about format, where the ID comes from, or whether the token is scoped to that compose.

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 'POST /compose.refreshToken', which restates the tool name in route form rather than explaining what refreshing a compose token accomplishes. It does not say whether a new token is minted, an existing one rotated, or what the token is used for.

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 at all on when to call this versus the many neighbouring token tools (application-refreshToken, scim-generateToken, user-generateToken) or versus other compose operations. The agent must guess the trigger condition entirely.

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