Skip to main content
Glama

delete_character

Remove D&D 5e characters permanently using ID or name. Supports batch deletion to manage multiple characters at once.

Instructions

Permanently delete a D&D 5e character by ID or name. Supports batch deletion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
characterIdNo
characterNameNo
batchNo

Implementation Reference

  • The 'delete_character' tool is registered here in toolRegistry with its name, description, JSON schema converted from Zod schema deleteCharacterSchema, and an async handler that validates input using deleteCharacterSchema, executes deleteCharacter function with validated args, and returns formatted success/error response with markdown content.
    delete_character: {
      name: 'delete_character',
      description: 'Permanently delete a D&D 5e character by ID or name. Supports batch deletion.',
      inputSchema: toJsonSchema(deleteCharacterSchema),
      handler: async (args) => {
        try {
          const validated = deleteCharacterSchema.parse(args);
          const result = deleteCharacter(validated);
    
          if (!result.success) {
            return error(result.error || 'Failed to delete character');
          }
    
          return success(result.markdown);
        } catch (err) {
          if (err instanceof z.ZodError) {
            const messages = err.errors.map(e => `${e.path.join('.')}: ${e.message}`).join(', ');
            return error(`Validation failed: ${messages}`);
          }
          const message = err instanceof Error ? err.message : String(err);
          return error(message);
        }
      },
    },
  • Handler function for 'delete_character' tool that performs Zod validation on input arguments, calls the core deleteCharacter helper function, checks for success, and formats the MCP response using success() or error() helpers.
    delete_character: {
      name: 'delete_character',
      description: 'Permanently delete a D&D 5e character by ID or name. Supports batch deletion.',
      inputSchema: toJsonSchema(deleteCharacterSchema),
      handler: async (args) => {
        try {
          const validated = deleteCharacterSchema.parse(args);
          const result = deleteCharacter(validated);
    
          if (!result.success) {
            return error(result.error || 'Failed to delete character');
          }
    
          return success(result.markdown);
        } catch (err) {
          if (err instanceof z.ZodError) {
            const messages = err.errors.map(e => `${e.path.join('.')}: ${e.message}`).join(', ');
            return error(`Validation failed: ${messages}`);
          }
          const message = err instanceof Error ? err.message : String(err);
          return error(message);
        }
      },
    },
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 mentions 'permanently delete' and 'batch deletion', which imply destructive and batch operations, but fails to detail critical aspects like permissions required, irreversible consequences, rate limits, or error handling. This leaves significant gaps in understanding the tool's behavior.

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 front-loaded with the core action and efficiently structured in two sentences: the first covers the primary deletion method, and the second adds batch support. Every sentence earns its place without redundancy, making it appropriately sized and clear.

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 tool's complexity as a destructive operation with 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, parameter usage, and return values, failing to provide sufficient context for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must compensate. It mentions parameters 'by ID or name' and 'batch deletion', which loosely map to 'characterId', 'characterName', and 'batch', but does not explain their semantics, relationships, or constraints (e.g., that 'batch' can handle up to 20 items). This adds minimal value beyond the schema's structure.

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'), the resource ('a D&D 5e character'), and the method ('by ID or name'), distinguishing it from sibling tools like 'get_character' or 'update_character'. It also mentions 'batch deletion' as an additional capability, making the purpose explicit and differentiated.

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, such as 'update_character' for modifications or 'get_character' for retrieval. It lacks context on prerequisites, like whether the character must be in a specific state, or exclusions, such as not using it during active encounters, leaving the agent without usage direction.

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/Mnehmos/mnehmos.chatrpg.game'

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