Skip to main content
Glama
Sign In
ctk

ctk

by zach-snell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

manage_users

Retrieve the current Confluence user or search for users by display name or email. Use 'get_current' for the logged-in user, or 'search' with a query to find specific users.

Instructions

Search and get Confluence users. Actions: 'get_current', 'search'

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": {
      "action": "<action>"
    },
    "name": "manage_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform: 'get_current', 'search'
queryNoSearch query — display name, email, etc. (for 'search')
limitNoMaximum results to return (for 'search', default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Search and get' – enough to imply read operations, but no mention of side effects, permissions, or data safety. The actions suggest no destructive behavior, but this is not explicitly stated.

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

Conciseness5/5

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

Extremely concise: a single sentence plus a list of actions. No wasted words; every element is essential and directly informs the agent's understanding.

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?

The description lacks information about return values for each action (no output schema), authentication requirements, or examples of usage. For a tool with two distinct actions, this is insufficient for an agent to accurately anticipate results.

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?

Schema description coverage is 100%, so the schema already adequately describes each parameter. The description adds minimal value by listing the actions, but does not provide additional semantics beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool searches and gets Confluence users, and lists the two specific actions: 'get_current' and 'search'. It distinguishes from sibling tools (e.g., manage_pages, manage_spaces) which handle different resources.

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 explicit guidance on when to use this tool versus alternatives, or when not to use it. The description only repeats the actions listed in the schema, providing no context about prerequisites, limitations, or comparison to other tools.

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

Deploy Server

Other Tools