Skip to main content
Glama
huseyindol

User Info MCP Server

by huseyindol

Kullanıcı Ekle

add_user

Add new users to the User Info MCP Server by providing name, email, and phone number for user information management.

Instructions

Yeni kullanıcı ekle

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesKullanıcının tam adı
emailYesE-posta adresi
phoneYesTelefon numarası

Implementation Reference

  • The handler function that executes the add_user tool logic. It calls userService.createUser and returns a formatted MCP response.
    static async handleAddUser({ name, email, phone }: { name: string; email: string; phone: string }): Promise<ToolResponse> {
      try {
        const result = await userService.createUser({ name, email, phone });
        
        return {
          content: [
            {
              type: "text",
              text: result.success 
                ? `${result.message}\n${JSON.stringify(result.data, null, 2)}`
                : result.error || "Kullanıcı oluşturulamadı",
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: "Kullanıcı oluşturma işleminde hata oluştu",
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the add_user tool: name, email, phone.
    export const AddUserInputSchema = {
      name: z.string().min(2).max(100).describe("Kullanıcının tam adı"),
      email: z.string().email().describe("E-posta adresi"),
      phone: z.string().min(10).max(20).describe("Telefon numarası")
    };
  • Registers the 'add_user' tool with the MCP server, specifying name, metadata, input schema, and handler.
    server.registerTool(
      "add_user",
      {
        title: "Kullanıcı Ekle",
        description: "Yeni kullanıcı ekle",
        inputSchema: AddUserInputSchema,
      },
      UserController.handleAddUser
    );
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. 'Yeni kullanıcı ekle' implies a mutation (creation) but doesn't disclose critical traits: whether it requires specific permissions, what happens on duplicate email/phone, if the operation is idempotent, rate limits, or what the response contains (e.g., user ID). For a write tool with zero annotation coverage, this is a significant gap.

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 phrase ('Yeni kullanıcı ekle') that is front-loaded and wastes no words. Every part earns its place by conveying the core action and resource without redundancy.

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 the complexity (a write operation with 3 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions, error handling, or return values, leaving the agent with insufficient context to use the tool effectively beyond basic parameter passing.

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%, with each parameter (name, email, phone) well-documented in the schema (e.g., 'Kullanıcının tam adı' for name). The description adds no parameter information beyond what's in the schema, so it meets the baseline of 3 for high schema coverage without compensating value.

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 'Yeni kullanıcı ekle' (Add new user) clearly states the verb 'ekle' (add) and resource 'kullanıcı' (user), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (like get_all_users, search_users_by_email, etc.), which are all read operations while this is a write operation. The distinction is implied but not explicitly stated.

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 prerequisites (e.g., admin permissions), when not to use it (e.g., for updating existing users), or refer to sibling tools like get_user_by_id for checking existing users before adding. The agent must infer usage from context 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/huseyindol/McpProjectScaffold'

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