Skip to main content
Glama
yarmijosp94

Evaluar MCP Server

by yarmijosp94

process_create

Create a new eTalent recruitment process in DRAFT status on the Evaluar platform. Returns the process ID for subsequent operations like assignments and management.

Instructions

Create a new eTalent process in DRAFT status. Returns the process ID for subsequent operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the process (e.g., 'Proceso eTalent - Asesor Ventas')
languageNoLanguage code (default: 'es')es
timeZoneNoTime zone (default: 'America/Bogota')America/Bogota

Implementation Reference

  • The main handler function for the 'process_create' tool, which performs authentication check, prepares payload, calls the API client, and returns a JSON-encoded status message.
    export async function handleProcessCreate(args: { name: string; language?: string; timeZone?: string }): Promise<string> {
      if (!isAuthenticated()) {
        return JSON.stringify({
          success: false,
          error: "Not authenticated. Please login first using auth_login.",
        });
      }
    
      try {
        const payload: CreateProcessPayload = {
          name: args.name,
          type: "etalent",
          language: args.language || "es",
          timeZone: args.timeZone || "America/Bogota",
        };
    
        const process = await createProcess(payload);
        return JSON.stringify({
          success: true,
          processId: process.id,
          name: process.name,
          status: process.status,
          message: "Process created in DRAFT status. Use process_assign_position to link a position.",
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          error: error instanceof Error ? error.message : "Unknown error",
        });
      }
    }
  • The tool definition and input schema for 'process_create', defining the expected name, optional parameters, and descriptions.
    export const processCreateTool = {
      name: "process_create",
      description: "Create a new eTalent process in DRAFT status. Returns the process ID for subsequent operations.",
      inputSchema: {
        type: "object" as const,
        properties: {
          name: {
            type: "string",
            description: "Name for the process (e.g., 'Proceso eTalent - Asesor Ventas')",
          },
          language: {
            type: "string",
            description: "Language code (default: 'es')",
            default: "es",
          },
          timeZone: {
            type: "string",
            description: "Time zone (default: 'America/Bogota')",
            default: "America/Bogota",
          },
        },
        required: ["name"],
      },
    };
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. It states the tool creates a new process and returns an ID, but doesn't mention permissions required, whether the creation is idempotent, error conditions, or rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its 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 perfectly concise with two sentences that each earn their place: the first states the core functionality and outcome, the second explains the return value. There's zero waste or redundancy, making it highly efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations and no output schema, the description provides basic purpose and return value but lacks details on error handling, authentication requirements, or what 'subsequent operations' entail. It's minimally viable but has clear gaps for a tool that creates resources.

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 the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, maintaining the baseline score of 3 for adequate but not enhanced parameter semantics.

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 ('Create a new eTalent process'), the resource ('eTalent process'), and the resulting status ('in DRAFT status'), distinguishing it from siblings like process_launch or process_assign_position by focusing on initial creation rather than subsequent operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating a new process in draft status, but lacks explicit guidance on when to use this versus alternatives like process_launch or prerequisites such as authentication. It mentions 'subsequent operations' but doesn't specify what those might be or when to choose this tool over others.

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/yarmijosp94/evaluar-mcp'

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