Skip to main content
Glama

install_community_persona

Add community personas to your local collection for the Persona MCP server, enabling AI to switch between expert personas with context detection and token-saving features.

Instructions

커뮤니티 페르소나를 로컬 컬렉션에 설치합니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes설치할 커뮤니티 페르소나 이름

Implementation Reference

  • Core handler function that installs a community persona by validating the name, reading from community directory, and writing to local persona directory.
    async function installCommunityPersona(name: string): Promise<string> {
      const validatedName = validatePersonaName(name);
      const communityPath = path.join(COMMUNITY_DIR, `${validatedName}.txt`);
      const localPath = path.join(PERSONA_DIR, `${validatedName}.txt`);
    
      try {
        const content = await fs.readFile(communityPath, 'utf-8');
        await fs.writeFile(localPath, content, 'utf-8');
        return localPath;
      } catch (error) {
        throw new Error(`Failed to install community persona "${validatedName}": ${(error as Error).message}`);
      }
    }
  • Zod schema for validating the tool input, requiring a 'name' field validated by personaNameSchema.
    export const installCommunityPersonaSchema = z.object({
      name: personaNameSchema,
    });
  • src/index.ts:436-448 (registration)
    Tool registration in the MCP server's listTools response, defining name, description, and input schema.
      name: 'install_community_persona',
      description: '커뮤니티 페르소나를 로컬 컬렉션에 설치합니다',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: '설치할 커뮤니티 페르소나 이름',
          },
        },
        required: ['name'],
      },
    },
  • MCP CallToolRequest handler case that parses arguments with schema, calls the install function, reads preview, and returns success message with usage instructions.
    case 'install_community_persona': {
      const validated = installCommunityPersonaSchema.parse(args);
      const installedPath = await installCommunityPersona(validated.name);
    
      // 간단한 프리뷰 제공
      const content = await readCommunityPersona(validated.name);
      const preview = content.split('\n').slice(0, 10).join('\n');
    
      return {
        content: [
          {
            type: 'text',
            text: `✅ Persona "${validated.name}" installed successfully!\n\n📁 Location: ${installedPath}\n\n📄 Preview:\n${preview}\n...\n\n💡 **How to use:**\n@persona:${validated.name} your question or task\n\nExample:\n@persona:${validated.name} help me with this code\n\n🎯 The persona will only activate when you use the @persona:${validated.name} trigger (Submarine Mode = 0 tokens otherwise)`,
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions installation into a local collection, hinting at a write operation, but lacks details on permissions, side effects, error conditions, or what 'installation' entails (e.g., copying, linking, or modifying).

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 without redundancy. It's appropriately sized and front-loaded, with no wasted words.

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 tool with no annotations, no output schema, and a write-like operation ('install'), the description is incomplete. It lacks information on what happens after installation, potential conflicts, or how this tool interacts with siblings like 'create_persona' or 'list_personas'.

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 'name' documented as 'name of the community persona to install'. The description adds no additional parameter semantics beyond this, 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 ('install') and target resource ('community persona'), specifying it's installed 'into the local collection'. However, it doesn't distinguish this from sibling tools like 'create_persona' or 'update_persona', which might have overlapping functionality.

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 'create_persona' or 'browse_community'. The description implies installation from a community source, but it doesn't specify prerequisites, exclusions, or contextual triggers 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/seanshin0214/persona-mcp'

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