Skip to main content
Glama
huseyindol

User Info MCP Server

by huseyindol

Tüm Kullanıcıları Getir

get_all_users

Retrieve a complete list of all users from the User Info MCP Server to access stored user data for management and analysis.

Instructions

Tüm kullanıcıların listesini getir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler function that fetches all users from the service layer and returns a formatted ToolResponse.
    static async handleGetAllUsers(): Promise<ToolResponse> {
      try {
        const result = await userService.getAllUsers();
        
        return {
          content: [
            {
              type: "text",
              text: result.success 
                ? JSON.stringify(result.data, null, 2)
                : result.error || "Bilinmeyen hata",
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: "Tool handler'da beklenmeyen hata oluştu",
            },
          ],
        };
      }
    }
  • Registers the 'get_all_users' tool with the MCP server, specifying title, description, empty input schema, and linking to the handler function.
    server.registerTool(
      "get_all_users",
      {
        title: "Tüm Kullanıcıları Getir",
        description: "Tüm kullanıcıların listesini getir",
        inputSchema: {},
      },
      UserController.handleGetAllUsers
    );
  • Service layer method that retrieves all users from the repository and handles errors, returning a standardized ServiceResult.
    async getAllUsers(): Promise<ServiceResult<User[]>> {
      try {
        const users = await userRepository.findAll();
        return {
          success: true,
          data: users,
          message: `${users.length} kullanıcı bulundu`
        };
      } catch (error) {
        return {
          success: false,
          error: "Kullanıcılar yüklenirken hata oluştu",
          data: []
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it indicates a read operation ('getir'), it doesn't specify whether this requires authentication, what format the list returns in (e.g., paginated or complete), or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 in Turkish that directly states the tool's function without any unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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's low complexity (0 parameters, no output schema), the description is minimally adequate but lacks details on behavioral aspects like authentication needs or return format. Without annotations or an output schema, the description should ideally provide more context about what 'list' entails, but it meets basic requirements for a simple retrieval 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 has 0 parameters with 100% coverage, so the schema already fully documents that no parameters are required. The description doesn't need to add parameter details, and it correctly implies no filtering parameters are needed. Baseline is 4 for tools with 0 parameters, as the description adequately matches the schema.

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 'Tüm kullanıcıların listesini getir' clearly states the tool's purpose as retrieving a list of all users, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from its sibling tools like search_users_by_email or get_user_by_id, which would require mentioning that this tool returns all users without filtering.

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. It doesn't mention that this is for retrieving all users without filtering, as opposed to using sibling tools like search_users_by_email for filtered searches or get_user_by_id for single-user retrieval. No explicit when/when-not instructions are provided.

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/huseyindol/McpProjectScaffold'

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