Skip to main content
Glama
aplaceforallmystuff

MCP Pickaxe Server

by aplaceforallmystuff
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

user_delete

Delete a user account from the Pickaxe platform by specifying their email address. This tool removes user data across multiple studio environments including PRODUCTION, STAGING, DEV, and MAIN.

Instructions

Delete a user by email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
studioNoStudio name to use. Available: STAGING, MAIN, DEV, PRODUCTION. Default: PRODUCTION
emailYesThe user's email address to delete

Implementation Reference

  • src/index.ts:559-567 (handler)
    The execution handler for the 'user_delete' tool. It constructs the API endpoint /studio/user/{email} and performs a DELETE request using the shared pickaxeRequest helper, returning the JSON response.
    case "user_delete": {
  const result = await pickaxeRequest(
    `/studio/user/${encodeURIComponent(args.email as string)}`,
    "DELETE",
    undefined,
    studio
  );
  return JSON.stringify(result, null, 2);
}
  • src/index.ts:361-375 (registration)
    The tool registration entry in the 'tools' array. This defines the tool's name, description, and input schema (including optional 'studio' parameter and required 'email'). The 'tools' array is returned by the ListTools handler.
    {
  name: "user_delete",
  description: "Delete a user by email.",
  inputSchema: {
    type: "object",
    properties: {
      studio: studioParam,
      email: {
        type: "string",
        description: "The user's email address to delete",
      },
    },
    required: ["email"],
  },
},
  • src/index.ts:364-374 (schema)
    Input schema for the 'user_delete' tool, specifying the parameters: optional 'studio' (references shared studioParam) and required 'email' string.
    inputSchema: {
  type: "object",
  properties: {
    studio: studioParam,
    email: {
      type: "string",
      description: "The user's email address to delete",
    },
  },
  required: ["email"],
},

Tool Definition Quality

C2.9/5.0
Behavior2/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 states the tool deletes a user but fails to mention critical details like whether this action is reversible, what permissions are required, what happens to associated data, or any rate limits. This leaves significant gaps for a destructive operation.

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, direct sentence with zero wasted words, making it highly efficient and front-loaded. It immediately conveys the core action without unnecessary elaboration.

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 destructive tool with no annotations and no output schema, the description is inadequate. It lacks essential context such as the tool's impact, return values, error conditions, or how it differs from sibling tools, leaving the agent with insufficient information for safe and effective use.

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%, so the schema fully documents both parameters ('studio' and 'email') with their types, descriptions, and requirements. The description adds no additional parameter information beyond what the schema provides, which is acceptable but not additive.

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 action ('Delete') and the resource ('a user by email'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'doc_delete' or 'user_update' beyond the resource type, which prevents a perfect score.

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 'user_update' or 'doc_delete', nor does it mention prerequisites, permissions, or consequences. It simply states what the tool does without context for selection.

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/aplaceforallmystuff/mcp-pickaxe'

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