Skip to main content
Glama

create_persona

Create custom AI personas with specific names and prompt content for the Persona MCP server, enabling on-demand expert role switching and context-aware interactions.

Instructions

새로운 페르소나 프로필을 생성합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes페르소나 이름 (예: default, professional, casual)
contentYes페르소나 프롬프트 내용

Implementation Reference

  • The main handler for the 'create_persona' tool. Validates the input arguments using createPersonaSchema and calls the savePersona helper function to persist the persona file. Returns a success message with the file location.
    case 'create_persona': {
      const validated = createPersonaSchema.parse(args);
      await savePersona(validated.name, validated.content);
      return {
        content: [
          {
            type: 'text',
            text: `페르소나 "${validated.name}"이(가) 생성되었습니다.\n위치: ${path.join(PERSONA_DIR, validated.name + '.txt')}`,
          },
        ],
      };
    }
  • Zod schema that validates the input for create_persona tool, requiring 'name' (validated by personaNameSchema) and 'content' (validated by personaContentSchema).
    export const createPersonaSchema = z.object({
      name: personaNameSchema,
      content: personaContentSchema,
    });
  • src/index.ts:323-340 (registration)
    Tool registration in the ListTools response, defining the name, description, and input schema for 'create_persona'.
    {
      name: 'create_persona',
      description: '새로운 페르소나 프로필을 생성합니다',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: '페르소나 이름 (예: default, professional, casual)',
          },
          content: {
            type: 'string',
            description: '페르소나 프롬프트 내용',
          },
        },
        required: ['name', 'content'],
      },
    },
  • Core helper function that implements the persona creation logic: validates name and content, constructs the file path in the persona directory, and writes the content to a .txt file.
      // 파일명 및 컨텐츠 검증
      const validatedName = validatePersonaName(name);
      const validatedContent = validatePersonaContent(content);
    
      const filePath = path.join(PERSONA_DIR, `${validatedName}.txt`);
      await fs.writeFile(filePath, validatedContent, 'utf-8');
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '생성합니다' (creates) implies a write/mutation operation, there's no information about permissions needed, whether creation is idempotent, what happens on duplicate names, or what the response contains. For a creation tool with zero annotation coverage, this is insufficient.

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 that states the core functionality without any wasted words. It's appropriately sized for a simple creation tool and gets straight to the point.

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 creation tool with no annotations and no output schema, the description is too minimal. It doesn't address what happens after creation, whether there are validation rules, how the created persona can be used, or any error conditions. Given the complexity of persona management and the existence of multiple sibling tools, more context would be helpful.

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 both parameters are well-documented in the schema itself. The description doesn't add any additional meaning about the parameters beyond what's already in the schema descriptions. This meets the baseline expectation when schema does the heavy lifting.

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 ('새로운...생성합니다' - creates new) and resource ('페르소나 프로필' - persona profile), making the purpose immediately understandable. It doesn't distinguish from siblings like 'update_persona' or 'install_community_persona', but the verb+resource combination is specific enough for basic understanding.

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 about when to use this tool versus alternatives like 'update_persona', 'install_community_persona', or 'chain_personas'. The description simply states what the tool does without context about appropriate use cases or prerequisites for creating a persona.

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