Skip to main content
Glama

user_list

Find Operaton users by ID, name, email, or group membership and return profile details for each matching account.

Instructions

Query Operaton users by id, firstName, lastName, email, or group membership. Returns profile info for each matching account.

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

Input Schema

NameRequiredDescriptionDefault
idNo
idInNo
emailNo
sortByNo
lastNameNo
emailLikeNo
firstNameNo
sortOrderNo
maxResultsNo
firstResultNo
lastNameLikeNo
firstNameLikeNo
memberOfGroupNo
memberOfTenantNo
potentialStarterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv1.3.0
    • addedInput schema / properties / email
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / emailLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / idIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / lastName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / lastNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / memberOfGroup
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / memberOfTenant
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / potentialStarter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

C2.7/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. It states that profile info is returned, but says nothing about pagination controls (maxResults/firstResult), sort behavior, whether empty result sets are normal, or access constraints.

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

Conciseness4/5

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

Two short sentences, front-loaded with the query capability and return shape. No filler, though the space savings come partly at the cost of documenting the many parameters.

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?

With 15 optional parameters, no annotations, and no output schema, the description is too thin to guide correct invocation; it covers only the basic identity filters and return summary.

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?

Schema description coverage is 0% across 15 parameters. The description names six filters (id, firstName, lastName, email, group membership), but leaves the Like variants, idIn, sortBy, sortOrder, maxResults, firstResult, memberOfTenant, and potentialStarter unexplained.

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?

Uses a specific verb+resource ("Query ... users") and names the filterable fields, so the plural/list intent is clear. It does not explicitly differentiate from the sibling user_getProfile, which is the main clarity gap.

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 implies use for finding users but gives no when-to-use/when-not guidance, no prerequisite or permission notes, and does not point to user_getProfile for a single-account lookup or to user_create/user_updateProfile alternatives.

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