Skip to main content
Glama
yusuferenkt

MCP JSON Database Server

by yusuferenkt

delete_user

Remove a user account from the JSON database by specifying their unique ID. This tool helps maintain accurate user records by deleting outdated or unnecessary entries.

Instructions

Kullanıcıyı siler

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSilinecek kullanıcının ID'si

Implementation Reference

  • Handler function that deletes a user by ID from the in-memory database (db.users array), using findIndex and splice, then persists via writeDatabase. No authentication check.
    case 'delete_user': {
      const { id } = args;
      const userIndex = db.users.findIndex(u => u.id === id);
      
      if (userIndex === -1) {
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({ error: 'Kullanıcı bulunamadı' })
          }]
        };
      }
    
      db.users.splice(userIndex, 1);
      await writeDatabase(db);
      
      return {
        content: [{
          type: 'text',
          text: JSON.stringify({ success: true, message: 'Kullanıcı silindi' })
        }]
      };
    }
  • Tool schema definition in the ListTools response, specifying input as object with required 'id' number field. No token required.
    {
      name: 'delete_user',
      description: 'Kullanıcıyı siler',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'number', description: 'Silinecek kullanıcının ID\'si' }
        },
        required: ['id']
      }
    },
Behavior1/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. 'Kullanıcıyı siler' only states the action without any details about permissions required, whether deletion is permanent or reversible, side effects (e.g., associated data cleanup), error conditions, or response format. For a destructive operation with zero annotation coverage, this is dangerously inadequate.

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

Conciseness2/5

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

The description is a single phrase 'Kullanıcıyı siler', which is overly concise to the point of under-specification. While it avoids verbosity, it fails to provide essential context for a destructive tool. Every sentence should earn its place, but this one doesn't deliver enough value—it's not conciseness but insufficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (destructive user deletion), lack of annotations, and no output schema, the description is severely incomplete. It doesn't address critical aspects like authentication needs, irreversible consequences, or what happens post-deletion. For a high-stakes operation among many sibling tools, this leaves the agent unprepared to use it safely or 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 input schema has 100% description coverage, with the single parameter 'id' clearly documented as 'Silinecek kullanıcının ID'si' (ID of the user to be deleted). The description doesn't add any parameter details beyond the schema, but with high schema coverage and only one parameter, the baseline is appropriately high. No compensation is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Kullanıcıyı siler' (Deletes the user) is a tautology that merely restates the tool name 'delete_user' in Turkish. While it clearly indicates the action (delete) and resource (user), it doesn't differentiate from sibling tools like 'update_user' or 'add_user' beyond the obvious verb difference. It lacks specificity about what 'delete' entails in this context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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., user must exist), exclusions (e.g., cannot delete self), or related tools like 'update_user' or 'list_users'. With siblings including user management tools, this omission is significant and leaves the agent guessing about appropriate contexts.

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/yusuferenkt/mcp-database'

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