Skip to main content
Glama

user_delete

Permanently delete user accounts from Crafty Controller. Requires superuser privileges to remove users by ID.

Instructions

Permanently delete a Crafty Controller user account. Requires superuser privileges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID to delete

Implementation Reference

  • The registration and handler implementation for the `user_delete` tool.
    server.tool(
      "user_delete",
      "Permanently delete a Crafty Controller user account. Requires superuser privileges.",
      { user_id: z.string().describe("User ID to delete") },
      async ({ user_id }) => {
        try {
          const data = await client.delete(`/users/${user_id}`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a destructive operation ('permanently delete') and specifies privilege requirements, which are crucial behavioral traits. However, it doesn't address potential consequences, confirmation steps, or whether the action is reversible, leaving some behavioral aspects unclear.

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 perfectly concise with two sentences that each earn their place: the first states the core action and resource, the second provides critical usage context. It's front-loaded with the most important information and contains zero wasted words.

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?

For a destructive tool with no annotations and no output schema, the description provides adequate but minimal information. It covers the destructive nature and privilege requirements, which are essential, but doesn't address return values, error conditions, or system impacts that would be helpful given the tool's high-stakes nature.

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 the single parameter 'user_id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides, so it meets the baseline expectation without adding extra value.

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 clearly states the specific action ('permanently delete') and resource ('Crafty Controller user account'), distinguishing it from sibling tools like user_get, user_list, user_update, and user_create. It uses precise language that leaves no ambiguity about the tool's function.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('Requires superuser privileges'), providing important context about authorization requirements. However, it doesn't specify when NOT to use it or mention alternatives like user_update for deactivation scenarios, which would be helpful for sibling differentiation.

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/HadiCherkaoui/crafty-mcp'

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