Skip to main content
Glama

delete_persona

Remove a persona profile from the Persona MCP server to manage expert personas and optimize system resources.

Instructions

페르소나 프로필을 삭제합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes삭제할 페르소나 이름

Implementation Reference

  • src/index.ts:359-372 (registration)
    Registration of the 'delete_persona' tool in the ListToolsRequestHandler, defining its name, description, and input schema.
    {
      name: 'delete_persona',
      description: '페르소나 프로필을 삭제합니다',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: '삭제할 페르소나 이름',
          },
        },
        required: ['name'],
      },
    },
  • Zod schema for validating the input arguments of the delete_persona tool, requiring a valid persona name.
    export const deletePersonaSchema = z.object({
      name: personaNameSchema,
    });
  • Handler logic in the CallToolRequestHandler switch statement that validates arguments using deletePersonaSchema, calls deletePersona, and returns success message.
    case 'delete_persona': {
      const validated = deletePersonaSchema.parse(args);
      await deletePersona(validated.name);
      return {
        content: [
          {
            type: 'text',
            text: `페르소나 "${validated.name}"이(가) 삭제되었습니다.`,
          },
        ],
      };
    }
  • Core helper function that validates the persona name and deletes the corresponding .txt file from the local persona directory.
    async function deletePersona(name: string): Promise<void> {
      const validatedName = validatePersonaName(name);
      const filePath = path.join(PERSONA_DIR, `${validatedName}.txt`);
      await fs.unlink(filePath);
    }
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 persona profile, implying a destructive mutation, but doesn't cover critical aspects like whether deletion is permanent, requires specific permissions, has side effects, or what happens to associated data. This leaves significant gaps for a mutation tool.

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 sentence in Korean that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 mutation with no annotations, no output schema, and incomplete behavioral disclosure, the description is inadequate. It fails to address key contextual elements like deletion permanence, error conditions, or return values, 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?

The schema description coverage is 100%, with the single parameter 'name' documented as '삭제할 페르소나 이름' (name of the persona to delete). The description adds no additional meaning beyond what the schema provides, so it meets the baseline 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 clearly states the action ('삭제합니다' - deletes) and the resource ('페르소나 프로필' - persona profile), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'update_persona' or 'chain_personas' in terms of scope or effect, 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?

No guidance is provided on when to use this tool versus alternatives like 'update_persona' or 'list_personas', nor does it mention prerequisites or consequences. The description merely states what it does without contextual usage instructions.

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/seanshin0214/persona-mcp'

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