Skip to main content
Glama
dvvolkovv

Human Design MCP Server

by dvvolkovv

get_human_design_definition

Retrieve Human Design definitions and meanings for components including type, authority, profile, gates, channels, and centers to understand your energetic blueprint.

Instructions

Получить определения и значения в Human Design

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentYesКомпонент Human Design для определения

Implementation Reference

  • The core handler function that executes the tool logic for 'get_human_design_definition'. It returns a JSON object with definitions for the specified Human Design component (type, authority, centers).
    async function getHumanDesignDefinition(component) {
      const definitions = {
        type: {
          manifestor: {
            name: 'Манифестор',
            strategy: 'Информировать',
            authority: 'Следовать своей силе',
            description: 'Манифесторы имеют закрытую и авторитетную ауру. Они приходят в этот мир, чтобы инициировать и воздействовать на других людей.',
          },
          generator: {
            name: 'Генератор',
            strategy: 'Отвечать',
            authority: 'Следовать своему отклику',
            description: 'Генераторы обладают открытой и притягивающей аурой. Их цель - найти работу, которая приносит им удовольствие.',
          },
          manifesting_generator: {
            name: 'Манифестирующий Генератор',
            strategy: 'Отвечать и информировать',
            authority: 'Следовать своему отклику',
            description: 'Манифестирующие Генераторы сочетают энергию Генератора с возможностью инициировать, как Манифестор.',
          },
          projector: {
            name: 'Проектор',
            strategy: 'Ждать приглашения',
            authority: 'Ждать признания других',
            description: 'Проекторы имеют сосредоточенную ауру. Их задача - направлять и управлять энергией Генераторов и Манифесторов.',
          },
          reflector: {
            name: 'Рефлектор',
            strategy: 'Ждать полного лунного цикла',
            authority: 'Ждать 28 дней для принятия решений',
            description: 'Рефлекторы имеют устойчивую, отталкивающую ауру. Они отражают энергию окружающих людей.',
          },
        },
        authority: {
          emotional: {
            name: 'Эмоциональная',
            description: 'Ждите, пока эмоции не выровняются, прежде чем принимать решения.',
          },
          sacral: {
            name: 'Сакральная',
            description: 'Слушайте своё тело и следуйте своему отклику.',
          },
          splenic: {
            name: 'Селезеночная',
            description: 'Доверяйте первым инстинктам и интуиции.',
          },
          ego_manifested: {
            name: 'Проявленный Эго',
            description: 'Следуйте обещаниям и обязательствам.',
          },
          ego_projected: {
            name: 'Проецируемый Эго',
            description: 'Ждите приглашения или признания.',
          },
          g_center: {
            name: 'G-Центр',
            description: 'Следуйте направлению любви.',
          },
          no_inner_authority: {
            name: 'Без внутренней власти',
            description: 'Окружайте себя правильными людьми.',
          },
          lunar: {
            name: 'Лунная',
            description: 'Ждите полный лунный цикл.',
          },
        },
        centers: [
          { number: 1, name: 'Root', ru_name: 'Корневой', type: 'pressure' },
          { number: 2, name: 'Sacral', ru_name: 'Сакральный', type: 'motor' },
          { number: 3, name: 'Solar Plexus', ru_name: 'Солнечное сплетение', type: 'motor' },
          { number: 4, name: 'Heart', ru_name: 'Сердечный', type: 'motor' },
          { number: 5, name: 'Throat', ru_name: 'Горловой', type: 'output' },
          { number: 6, name: 'Ajna', ru_name: 'Аджана', type: 'awareness' },
          { number: 7, name: 'Head', ru_name: 'Головной', type: 'pressure' },
          { number: 8, name: 'Spleen', ru_name: 'Селезенка', type: 'awareness' },
          { number: 9, name: 'G', ru_name: 'G-центр', type: 'identity' },
        ],
      };
    
      return definitions[component] || { error: 'Unknown component' };
    }
  • Tool registration in the ListTools handler, defining the name, description, and input schema for 'get_human_design_definition'.
    {
      name: 'get_human_design_definition',
      description: 'Получить определения и значения в Human Design',
      inputSchema: {
        type: 'object',
        properties: {
          component: {
            type: 'string',
            enum: ['type', 'authority', 'profile', 'gates', 'channels', 'centers'],
            description: 'Компонент Human Design для определения',
          },
        },
        required: ['component'],
      },
    },
  • Input schema definition for the 'get_human_design_definition' tool, specifying the 'component' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        component: {
          type: 'string',
          enum: ['type', 'authority', 'profile', 'gates', 'channels', 'centers'],
          description: 'Компонент Human Design для определения',
        },
      },
      required: ['component'],
    },
  • Dispatch handler in CallToolRequestSchema that invokes the getHumanDesignDefinition function and formats the response.
    if (name === 'get_human_design_definition') {
      const definitions = await getHumanDesignDefinition(args.component);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(definitions, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it 'gets definitions and meanings' without specifying whether this is a read-only operation, what format the output takes, whether there are rate limits, authentication requirements, or other behavioral traits. This leaves significant gaps for an agent to understand how to use it effectively.

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, concise sentence in Russian that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple tool with one parameter and no complex behavior to explain.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., format, structure of definitions), how errors are handled, or how it differs from the sibling tool. For a tool with no structured output documentation, the description should provide more context about expected results.

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 input schema has 100% description coverage with a clear enum for the 'component' parameter, so the schema does the heavy lifting. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain what each component type means or provide examples). This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Получить определения и значения в Human Design' (Get definitions and meanings in Human Design), which is clear but vague. It specifies the domain (Human Design) and general action (get definitions/meanings), but doesn't distinguish it from the sibling tool 'calculate_human_design' or provide specific details about what kind of definitions are retrieved.

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 the sibling tool 'calculate_human_design'. There's no mention of prerequisites, alternatives, or specific contexts where this tool is appropriate versus others. The user must infer usage from the name and description alone.

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/dvvolkovv/MCP_Human_design'

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