Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

confluence_user_search

Search Confluence users by display name or email. Set limit to 0 to retrieve every match, or leave default for up to 25.

Instructions

Search Confluence users by display name or email. limit of 0 returns every match; defaults to 25. Mirrors omni-dev atlassian confluence user 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": {
      "query": "<query>"
    },
    "name": "confluence_user_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (0 = unlimited). Defaults to 25.
queryYesSearch text; matches display name or email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `confluence_user_search` tool."
    • removedInput schema / title
      Removed value: -"ConfluenceUserSearchParams"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states the search criteria and limit behavior, but does not disclose return format, pagination details beyond limit, authentication requirements, or potential rate limits. For a simple search tool, this is adequate but minimal.

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?

The description consists of two short sentences, front-loading the purpose and then providing additional parameter detail. There is no redundant or extraneous information. Every sentence serves a clear purpose.

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

Completeness3/5

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

Given the tool has only two parameters, no output schema, and no nested objects, the description provides the essential purpose and parameter behavior. However, it lacks information about the return value structure (e.g., list of user objects, fields included), which would be helpful for an agent invoking the tool.

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

Parameters4/5

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

The input schema already describes both parameters with 100% coverage. The description adds value by clarifying the special behavior of 'limit=0' (unlimited results) and the default value of 25, which goes beyond the schema's description.

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

Purpose4/5

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

The description clearly states the tool searches Confluence users by display name or email, which matches the tool name. However, it does not explicitly differentiate from the sibling tool confluence_user_get, which might retrieve a single user by ID. The verb 'search' and the resource 'Confluence users' are specific and unambiguous.

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?

The description includes parameter behavior (limit of 0 returns all matches, default 25) and a reference to a CLI command, but it does not provide guidance on when to use this tool versus alternatives like confluence_user_get or jira_user_search. No 'when to use' or 'when not to use' context is given.

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