Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

listMembers

Retrieve and filter DICloak workspace members by role, status, authority, remark, or creation date, with pagination and optional detail, to audit or manage team access.

Instructions

List members

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listMembers"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
userNo
detailNo
remarkNo
statusNo
page_noNo
role_idNo
authorityNoAuthority (e.g., ADMIN/MANAGER/MEMBER/SUPER_ADMIN)
page_sizeNo
env_group_idNo
end_create_timeNo
start_create_timeNo

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 and supplies nothing: no read-only confirmation, no pagination or default page_size behavior, no permission requirements, and no sense of result size or ordering. For a 12-parameter listing tool this is a total gap.

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 are technically concise, but this is under-specification rather than economy; there is no front-loaded scope, no structure, and nothing an agent can act on beyond the tool name.

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 12 parameters, no annotations, no output schema, and near-zero schema coverage, the description would need to explain filtering semantics, pagination, and return shape. It does none of these, leaving the definition unusable for correct invocation.

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?

Schema description coverage is 8% — only 'authority' is documented in the schema — and the description adds zero meaning for the other 11 parameters such as all, detail, status, role_id, remark, or the time-window bounds. An agent cannot tell whether status/role_id filter results, whether detail expands payloads, or how all interacts with the other filters.

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?

"List members" restates the tool name with no additional specificity. It does not say whose members (organization, environment, group), what the listing returns, or how it differs from siblings such as listEnvGroups or listEnvs.

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?

The description gives no indication of when to use this tool, when not to, or which sibling to pick instead. An agent must infer that it enumerates members from the name alone, with no exclusions for filtering or pagination scenarios.

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