Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

deleteMember

Deletes a member from the DICloak Local API by ID, enabling removal of user access or membership records when no longer needed.

Instructions

Delete 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": {
      "id": "<id>"
    },
    "name": "deleteMember"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

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 it discloses nothing. For a destructive delete it omits whether the operation is irreversible, what related data is removed or orphaned, permission requirements, and confirm-on-missing behavior — all critical for an agent deciding whether to call it.

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 represent under-specification rather than economy of expression. There is no structure, no front-loaded context, and no information an agent can act on beyond the title.

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 destructive one-parameter mutation with zero annotations, no output schema, and 0% parameter documentation requires far more description than this. Nothing about effects, return values, or failure modes is covered.

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 0%, so the single required parameter "id" is undocumented in both the schema and the description. The description never clarifies whether this is a member ID, user ID, or email, nor the expected format, which the description was obligated to compensate for given the coverage gap.

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?

"Delete member" is a verb+resource restatement that adds essentially nothing beyond the tool name deleteMember. It does not identify what a "member" is (org member? environment member?), what scope the deletion applies to, or how it differs from siblings like patchMember, updateMember, or saveMember.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling list contains updateMember, patchMember, getMemberInfo, and getMemberRoles, but the description gives the agent no basis for choosing deletion over modification or inspection.

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