Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

updateMember

Updates an existing member's account details, role, authority, environment group access, and status via the DICloak Local API.

Instructions

Update member (PUT)

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": {
      "id": "<id>",
      "email": "<email>",
      "name": "<name>",
      "authority": "<authority>",
      "role_id": "<role_id>",
      "passwd": "<passwd>"
    },
    "name": "updateMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYesMember name
typeNoMember type, default INTERNAL
emailYesAccount used for login. When creating an EXTERNAL member, a valid email format is required and an email will be sent.
phoneNo
passwdYesMember password. Important: required when creating INTERNAL members; not required for EXTERNAL members.
remarkNo
statusNoMember status, default ENABLED
role_idYesMember role ID; obtain via role management API.
agent_idNo
authorityYesMember role; default is MEMBER
time_zoneNoMember timezone. For China usually Asia/Shanghai; set according to user's network environment to display correct local time on login.
manager_idNo
disuse_timeNoMember disable time, used with disuse_enable. Example: 2025-11-21 18:31:47
expiry_modeNoMember expiry mode, default INSTANT. INSTANT means immediate; LONGIN_START means effective after first login.
expiry_timeNoMember expiry days, used with expiry_mode=LONGIN_START. Number of days after activation before expiry, default 30
all_env_groupNo
disuse_enableNoWhether member disable feature is enabled (default false). True means disable feature enabled; false means disabled.
env_group_idsNoEnvironment group IDs the member has access to. Retrieve IDs from the environment group API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the entire behavioral burden, and it discloses nothing. It does not say that a PUT may overwrite or clear fields not included in the payload, does not mention that a password field is required, and does not describe permission or side-effect implications for a write operation touching 19 fields.

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?

Three words are certainly compact, but brevity here is under-specification rather than conciseness: there is no informative content to front-load. Nothing in the text earns its place beyond the tool name the agent already has.

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 19-parameter, 6-required mutation tool with no annotations and no output schema, the description supplies nothing an agent needs to invoke it safely. It should at minimum state replacement semantics, required-field behavior, and the consequences of omitted optional fields.

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?

The schema documents roughly 68% of 19 parameters and carries the enum meanings, while the description contributes zero parameter meaning. It does not clarify the required list (id, email, name, authority, role_id, passwd) nor the PUT-specific question of which of the remaining 13 optional fields are reset when omitted.

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?

"Update member (PUT)" restates the tool name plus an HTTP verb and adds no scope, no affected fields, and no distinction from siblings such as patchMember or saveMember. The only marginal information is "(PUT)", which is left unexplained, so an agent cannot tell whether this is a full replacement or a partial edit.

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 prerequisites, and no mention of the clearly related alternatives (patchMember, saveMember, deleteMember) that appear in the sibling list. Given that PUT semantics differ materially from PATCH, the absence of any routing guidance is actively risky rather than merely absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.