Skip to main content
Glama

show_users

List all users in your Anaplan tenant with optional sorting, search by name or ID, and limit results.

Instructions

List all users in the tenant

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field (e.g., '%2BemailAddress' for ascending email)
limitNoMax items to return (default 50, max 1000)
searchNoFilter by name or ID (case-insensitive substring match)

Implementation Reference

  • The 'show_users' tool handler. Calls apis.users.list(sort) and formats results as a table with Name, Email, Active, and ID columns, supporting limit and search pagination.
    server.tool("show_users", "List all users in the tenant", {
      sort: z.string().optional().describe("Sort field (e.g., '%2BemailAddress' for ascending email)"),
      ...paginationParams,
    }, async ({ sort, limit, search }) => {
      const users = await apis.users.list(sort);
      return tableResult(users, [
        { header: "Name", key: "firstName" },
        { header: "Email", key: "email" },
        { header: "Active", key: "active" },
        { header: "ID", key: "id" },
      ], "users", { limit, search });
    });
  • The paginationParams schema used by show_users, defining optional 'limit' and 'search' parameters.
    const paginationParams = {
      limit: z.number().optional().describe("Max items to return (default 50, max 1000)"),
      search: z.string().optional().describe("Filter by name or ID (case-insensitive substring match)"),
    };
  • The tool's input schema including optional 'sort' parameter and spread paginationParams.
    server.tool("show_users", "List all users in the tenant", {
      sort: z.string().optional().describe("Sort field (e.g., '%2BemailAddress' for ascending email)"),
      ...paginationParams,
  • src/server.ts:54-57 (registration)
    Registration of exploration tools (including show_users) via registerExplorationTools. The users API is passed as part of the apis object.
    registerExplorationTools(server, {
      workspaces, models, modules, lists, imports, exports, processes, files, actions, transactional, modelManagement, dimensions,
      calendar, versions, users,
    }, resolver);
  • The UsersApi.list() method — the underlying API helper that performs the HTTP GET to /users endpoint with optional sort parameter.
    async list(sort?: string) {
      const suffix = sort ? `?sort=${sort}` : "";
      return this.client.getAll<any>(`/users${suffix}`, ["users", "user"]);
    }
Behavior2/5

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

With no annotations, the description should disclose behavioral traits but only says 'List all users'. It omits read-only nature, output format, pagination, or any constraints beyond what's in the schema.

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 description is a single sentence, which is concise but lacks necessary details, making it slightly under-specified for a tool with optional 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?

Given no output schema and no behavioral annotations, the description is incomplete. It does not explain return values, pagination behavior, or how the listing is scoped.

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 documents all parameters. The description adds no extra meaning beyond 'List all users in the tenant'.

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?

The description explicitly states 'List all users in the tenant', which is a specific verb and resource, clearly distinguishing it from sibling tools like show_userdetails.

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 guidance is provided on when to use this tool versus alternatives (e.g., show_userdetails, lookup_dimensionitems), nor any prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/larasrinath/anaplan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server