Skip to main content
Glama
SLdragon

MCP User Profile Management Server

by SLdragon

list_users

Retrieve all user profiles stored in the system to view and manage user information.

Instructions

List all user profiles currently stored in the system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_users' tool. It imports storage dynamically, retrieves the list of users, formats them in a JSON response, and returns a success message or error.
    async () => {
      try {
        const { storage } = await import('../storage.js');
        return utils.createSuccessResponse(
          `All user profiles (${storage.users.length} total):\n${JSON.stringify(storage.users, null, 2)}`
        );
      } catch (error) {
        return utils.createErrorResponse(`Error listing users: ${error.message}`);
      }
    }
  • Registers the 'list_users' tool on the MCP server using server.tool(), providing the tool name, description, empty input schema (no parameters required), and the handler function.
    return server.tool(
      "list_users",
      "List all user profiles currently stored in the system",
      {},
      async () => {
        try {
          const { storage } = await import('../storage.js');
          return utils.createSuccessResponse(
            `All user profiles (${storage.users.length} total):\n${JSON.stringify(storage.users, null, 2)}`
          );
        } catch (error) {
          return utils.createErrorResponse(`Error listing users: ${error.message}`);
        }
      }
    );
  • index.js:17-17 (registration)
    Top-level call to listUsersTool(server) in the main server setup, which triggers the registration of the 'list_users' tool.
    listUsersTool(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but provides no information about permissions required, rate limits, pagination behavior, response format, or whether this operation has side effects. For a list operation with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 is a single, efficient sentence that communicates the core purpose without unnecessary words. It's front-loaded with the essential information and contains zero redundant or verbose elements. Every word earns its place in this minimal but complete statement of function.

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?

For a list operation with no annotations and no output schema, the description is insufficiently complete. It doesn't address what information is returned about users, whether results are paginated, what permissions are required, or how this differs meaningfully from 'search_users'. The agent lacks critical context needed to use this tool effectively.

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 tool has zero parameters with 100% schema description coverage, so the schema fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist. Baseline for zero parameters is 4, as the description correctly focuses on the tool's purpose rather than non-existent parameters.

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 verb ('List') and resource ('all user profiles'), making the purpose immediately understandable. It distinguishes from 'search_users' by specifying 'all' rather than filtered results. However, it doesn't explicitly mention the system scope or differentiate from sibling tools beyond the implicit 'all' vs 'search' distinction.

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 provides no guidance on when to use this tool versus alternatives like 'search_users' or 'create_user_profile'. It doesn't mention prerequisites, context for retrieving all users versus filtered subsets, or any limitations on usage scenarios. The agent must infer usage from the tool name alone.

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/SLdragon/mcp-elicitation-server'

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