Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

saveMember

Create a DICloak member with required email, name, role, and password, plus optional status, timezone, and environment group access settings.

Instructions

Create member

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

Input Schema

NameRequiredDescriptionDefault
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

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only conveys that this is a create/mutation operation. It omits everything an agent needs: whether INTERNAL vs EXTERNAL changes required fields, that an invitation email is sent to EXTERNAL members, defaults for status/authority/expiry_mode, permission requirements, and what happens on duplicate email.

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?

Two words is technically minimal but reflects under-specification rather than conciseness. There is no front-loaded explanation of the operation, its variants, or key constraints.

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 an 18-parameter creation tool with no annotations and no output schema, the description is wholly inadequate: it gives no field guidance, no conditional logic between INTERNAL/EXTERNAL modes, and no indication of the result of a successful call.

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 coverage is 72%, leaving several parameters (phone, remark, agent_id, manager_id, all_env_group) undocumented in both schema and description. The description contributes nothing beyond the schema despite the notable validation rules the schema itself encodes, so it fails to compensate for the remaining gap on an 18-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create member" gives a verb and resource that match the tool name, but says nothing about scope, what kind of member is created, or how it differs from siblings like updateMember, patchMember, or saveEnvGroup. An agent can infer creation from the name alone; the description adds essentially no discriminating detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus updateMember or patchMember, and no mention of prerequisites such as needing a role_id or existing env group IDs before calling. The agent must infer creation-vs-update from the tool name only.

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