Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

patchMember

Update an existing DICloak member's profile, role, status, password, access groups, and expiry settings via a PATCH request.

Instructions

Patch member (PATCH)

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": "patchMember"
  }
}

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; for PATCH, md5 hashing of provided password is needed for 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 provided, so the description carries the full burden, yet it discloses nothing about mutation semantics, required permissions, whether unspecified fields are preserved, or side effects. The single word "PATCH" plus the tool name is all the behavioral information given.

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 text is short but this is under-specification rather than conciseness; three words with a parenthetical HTTP verb provide no structure or front-loaded purpose for a 19-parameter tool.

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 mutation endpoint with no annotations and no output schema, the description is far too thin. It omits partial-update behavior, identity/role constraints, and any indication of what a successful patch returns.

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?

With 19 parameters and only 68% schema description coverage, the description needed to compensate but adds nothing. It does not explain required fields (email, name, authority, role_id, passwd), how passwd hashing applies on PATCH, or the expiry_mode/disuse_enable interactions — all of which the schema only partially documents.

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 "Patch member (PATCH)", which merely restates the tool name and HTTP verb. It does not say what a patch does to a member (partial update? full replace?) or distinguish it from the sibling tools saveMember, updateMember, and deleteMember.

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 guidance whatsoever on when to use patchMember versus saveMember or updateMember, nor any stated preconditions. An agent must guess which mutation tool applies.

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