Skip to main content
Glama
yarmijosp94

Evaluar MCP Server

by yarmijosp94

process_launch

Launch eTalent recruitment processes on the Evaluar platform by providing a process ID after assigning a position, returning a summary URL for tracking.

Instructions

Launch an eTalent process. The process must have a position assigned first. Returns the summary URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processIdYesThe ID of the process to launch

Implementation Reference

  • The handler function that executes the logic to launch an eTalent process by calling launchProcess.
    export async function handleProcessLaunch(args: { processId: string }): Promise<string> {
      if (!isAuthenticated()) {
        return JSON.stringify({
          success: false,
          error: "Not authenticated. Please login first using auth_login.",
        });
      }
    
      try {
        const summaryUrl = await launchProcess(args.processId);
        return JSON.stringify({
          success: true,
          processId: args.processId,
          summaryUrl,
          message: "Process launched successfully!",
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          error: error instanceof Error ? error.message : "Unknown error",
        });
      }
    }
  • The tool definition (schema) for process_launch, specifying the name, description, and input parameters.
    export const processLaunchTool = {
      name: "process_launch",
      description: "Launch an eTalent process. The process must have a position assigned first. Returns the summary URL.",
      inputSchema: {
        type: "object" as const,
        properties: {
          processId: {
            type: "string",
            description: "The ID of the process to launch",
          },
        },
        required: ["processId"],
      },
    };
Behavior3/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 mentions the prerequisite (position assignment) and the return value (summary URL), which adds useful context beyond basic functionality. However, it doesn't address important behavioral aspects like error conditions, authentication requirements, or what happens during the launch operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately brief (two sentences) and front-loaded with the core functionality. Both sentences provide valuable information (the action and the prerequisite, then the return value), with no wasted words or redundant information.

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?

For a single-parameter tool with no annotations and no output schema, the description provides the essential information about what the tool does, a prerequisite, and what it returns. However, it lacks details about the launch operation's behavior, potential side effects, or error handling that would be helpful for an agent to use it correctly.

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 the single parameter 'processId' clearly documented in the schema. The description doesn't add any additional parameter information beyond what the schema already provides, so it meets the baseline expectation but doesn't enhance parameter understanding.

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 ('Launch an eTalent process') and resource ('eTalent process'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'process_create' or 'process_assign_position' beyond the launch action.

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 provides one important prerequisite ('The process must have a position assigned first'), which gives some context for when to use this tool. However, it doesn't offer guidance on when to choose this tool versus alternatives like 'process_create' or 'process_assign_position', nor does it specify when NOT to use it.

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