Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getMemberRoles

List member roles in DICloak with optional filters for member ID or role name, plus pagination and detail views. Use it to retrieve role assignments for access management.

Instructions

List roles

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

Input Schema

NameRequiredDescriptionDefault
allNo
nameNo
detailNo
remarkNo
page_noNo
member_idNo
page_sizeNo

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 full burden of behavioral disclosure, and it discloses nothing. It does not say whether the operation is read-only, whether results are paginated, what permissions are needed, or what happens with the all/detail flags.

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 statement, no structure, and nothing an agent can act on.

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 seven-parameter tool with no annotations, no output schema, and no parameter documentation requires substantially more description than this. An agent cannot determine filtering behavior, paging defaults, or result shape from "List roles".

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% across seven parameters, including ambiguous flags (all, detail) and paging controls (page_no, page_size), yet the description explains none of them. The single phrase "List roles" adds zero meaning beyond the bare property names.

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 roles" merely re-expands the tool name getMemberRoles into a verb-plus-noun phrase without adding specificity. It does not indicate whether this returns roles for a single member, all members, or the role catalog, nor how it differs from siblings like getMemberInfo.

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 when-to-use guidance, no exclusions, and no mention of alternatives. The presence of member_id in the schema hints at per-member scoping, but the description never states the condition under which this tool should be chosen over getMemberInfo or updateMember.

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