Skip to main content
Glama
yarmijosp94

Evaluar MCP Server

by yarmijosp94

process_assign_position

Associate a position with an existing eTalent recruitment process on the Evaluar platform using position, agency, and department IDs.

Instructions

Associate a position with an existing eTalent process. Get position details from position_search first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processIdYesThe ID of the process (from process_create)
positionIdYesThe ID of the position (from position_search)
agencyIdYesThe agency ID (from position_search)
departmentIdYesThe department ID (from position_search)

Implementation Reference

  • The handler function for the process_assign_position tool, which authenticates the request and calls the API to assign the position.
    export async function handleProcessAssignPosition(args: AssignPositionPayload): Promise<string> {
      if (!isAuthenticated()) {
        return JSON.stringify({
          success: false,
          error: "Not authenticated. Please login first using auth_login.",
        });
      }
    
      try {
        await assignPositionToProcess(args);
        return JSON.stringify({
          success: true,
          message: "Position assigned to process successfully. Use process_launch to start the process.",
          processId: args.processId,
          positionId: args.positionId,
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          error: error instanceof Error ? error.message : "Unknown error",
        });
      }
    }
  • The tool schema definition for process_assign_position.
    export const processAssignPositionTool = {
      name: "process_assign_position",
      description: "Associate a position with an existing eTalent process. Get position details from position_search first.",
      inputSchema: {
        type: "object" as const,
        properties: {
          processId: {
            type: "string",
            description: "The ID of the process (from process_create)",
          },
          positionId: {
            type: "string",
            description: "The ID of the position (from position_search)",
          },
          agencyId: {
            type: "string",
            description: "The agency ID (from position_search)",
          },
          departmentId: {
            type: "string",
            description: "The department ID (from position_search)",
          },
        },
        required: ["processId", "positionId", "agencyId", "departmentId"],
      },
    };
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. It mentions that it 'associates' a position, implying a mutation/write operation, but doesn't disclose critical details like required permissions, whether the association is reversible, error conditions, or what happens if parameters are invalid. For a mutation tool with zero annotation coverage, this is a significant gap.

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 two concise sentences with zero waste. The first sentence states the purpose, and the second provides essential usage guidance, making it front-loaded and efficiently structured.

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 the tool's complexity (a mutation with 4 required parameters), lack of annotations, and no output schema, the description is minimally adequate. It covers purpose and basic usage but lacks details on behavioral traits, error handling, or return values. It meets the minimum viable threshold but has clear gaps in completeness.

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 schema description coverage is 100%, so the schema already documents all four parameters with their sources (e.g., 'from process_create', 'from position_search'). The description adds no additional parameter semantics beyond what the schema provides, but it reinforces the dependency on 'position_search' for position details, which aligns with the schema. Baseline 3 is appropriate when the 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 ('Associate a position with an existing eTalent process') and specifies the resource ('eTalent process'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from potential siblings like 'process_create' or 'process_launch' beyond the specific association action.

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

Usage Guidelines4/5

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

The description provides clear contextual guidance by stating 'Get position details from position_search first,' which implies a prerequisite workflow. It doesn't explicitly state when not to use this tool or name alternatives, but the guidance is practical and helpful for correct usage.

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