Skip to main content
Glama
MCP Dokploy Online
by igoruam

organization-updateMemberRole

Idempotent

Updates an organization member’s role by member ID, letting administrators adjust permissions and access levels as responsibilities change.

Instructions

POST /organization.updateMemberRole

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": {
      "memberId": "<memberId>",
      "role": "<role>"
    },
    "name": "organization-updateMemberRole"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
memberIdYes

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 idempotentHint=true and openWorldHint=true, so the safety profile is partly carried by structured fields. The description adds nothing further: no mention of required permissions, whether the change is immediate or takes effect on next login, or which roles are assignable.

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 single line is short but not informative — it front-loads an HTTP verb and route instead of the effect of the call. Brevity here is under-specification rather than conciseness.

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?

A mutation to organization membership with no output schema, no parameter documentation, and no behavioral notes is not adequately described by a route string. An agent cannot call it correctly without guessing the accepted role values.

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?

Both parameters (memberId, role) are required with 0% schema description coverage, so the description must compensate and does not. It never states that role expects a role identifier/slug, nor which values are valid, leaving an agent to guess the single most consequential input.

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 "POST /organization.updateMemberRole", which restates the tool name in HTTP-route form rather than explaining what changes. An agent can infer that a member's role is modified, but nothing distinguishes it from siblings such as customRole-update or organization-update.

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 when-to-use, prerequisites, or alternative guidance is present. The definition gives no signal about when role assignment should be done here versus creating or updating a custom role via the customRole-* siblings.

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