Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getMemberInfo

Retrieves detailed information for a specific member by ID, enabling AI assistants to look up member records in DICloak.

Instructions

Get member details

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/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 and discloses almost nothing: no statement that it is a read-only lookup, no indication of what happens with an unknown id, no return-shape or error behavior. Only the implied "get = read" convention conveys any behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is three words and front-loaded, so there is no wasted phrasing, but brevity here reflects under-specification rather than precision. Nothing useful is prioritized because almost nothing is said.

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 lookup tool sitting among many similarly named member tools (getMemberRoles, deleteMember, patchMember, updateMember), and with no annotations, no output schema, and an undocumented parameter, the definition leaves the agent without the information needed to call it correctly.

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?

The single required parameter has 0% schema description coverage, and the description does not clarify that "id" is a member identifier (as opposed to a workspace or environment id) or what format it takes. The only hint comes from the word "member" in the title text, not from meaningful parameter documentation.

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?

"Get member details" restates the tool name and adds only the vague object "details". It does not say which member fields are returned or how it differs from neighbors like getMemberRoles or getEnvInfo, leaving an agent unable to choose confidently.

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 prerequisites (e.g., authentication or required permissions), and no mention of an alternative such as getMemberRoles for role data. Usage must be inferred entirely from the name.

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