Skip to main content
Glama
keycrm-mcp

keycrm-mcp

by IgorShutko

users

List team members with roles and permissions, or retrieve role and permission details for access management.

Instructions

Team: list (members with roles), roles, permissions.

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

Input Schema

NameRequiredDescriptionDefault
actionNolist

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 does not meet it. It never states that this is a read-only operation, whether it requires admin or team-level authorization to view roles and permissions, or whether results are paginated. Only the word "list" implies a non-mutating read.

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?

It is very short, but it is not structured: it is a compressed fragment with parenthetical nesting and no front-loaded statement of purpose. Brevity here comes from under-specification rather than from disciplined editing, so the sentence does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but with zero annotation coverage and an undocumented action parameter, the description should do more. It never clarifies the relationship between listing members, listing roles, and listing permissions, nor what authorization is needed to see role data.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one optional parameter, action, with 0% schema description coverage and a default of "list". The description partially compensates by enumerating what appear to be its possible values (list members with roles, roles, permissions), which gives the agent a usable mental model of the action switch. It still does not state the exact allowed string values or what each returns.

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?

The description names a resource area (team membership) and three things it exposes: members with roles, roles, and permissions, with "list" as the verb. However, the phrasing is a telegraphic fragment rather than a sentence, and the tool name "users" does not make it obvious that this also returns roles and permissions. An agent can guess the domain but must infer the exact behavior.

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 explicit when-to-use guidance, no exclusions, and no named alternative among the many sibling tools (clients, comments, audit, settings, etc.). The parenthetical "list (members with roles)" hints at a default listing behavior but does not state when an agent should choose this tool over, for example, settings or audit for permission-related questions.

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