Skip to main content
Glama
MCP Dokploy Online
by igoruam

scim-generateToken

Idempotent

Generates a SCIM token for the specified identity provider, enabling provisioning and user lifecycle synchronization with Dokploy.

Instructions

POST /scim.generateToken

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": {
      "providerId": "<providerId>"
    },
    "name": "scim-generateToken"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerIdYes

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 only supply idempotentHint and openWorldHint; the description adds nothing about token lifetime, scope, whether existing tokens are invalidated, or whether repeated calls return the same token (which is exactly what idempotentHint=true leaves ambiguous for a 'generate' operation). For a mutation-style credential operation the description carries information debt rather than paying it down.

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 this is under-specification rather than conciseness; a route string is not a structured explanation and nothing is front-loaded about purpose or effect.

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, an undocumented required parameter, and thin annotations, the description should explain the token's scope and the effect of calling it. It provides none of that, leaving the definition unusable without guessing.

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?

The single required parameter providerId has 0% schema description coverage, and the description contributes no meaning at all — not what a provider is, nor its format or where to obtain it. The description must compensate here and does not.

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?

"POST /scim.generateToken" only restates the HTTP method and route already implied by the name scim-generateToken. It does not say what the generated token is for, what it grants access to, or how it relates to siblings such as user-generateToken or application-refreshToken.

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 when-to-use guidance, no prerequisite or permission note, and no indication of when a caller should prefer this over the sibling token tools. The agent is left to infer everything from the name alone.

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