Skip to main content
Glama
yarmijosp94

Evaluar MCP Server

by yarmijosp94

auth_login

Authenticate users with username and password to access Evaluar recruitment platform features, returning authentication status and token information.

Instructions

Authenticate with Evaluar using username and password. Returns success status and masked token info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesEmail address for Evaluar account
passwordYesPassword for Evaluar account

Implementation Reference

  • The handler function for the auth_login tool, which performs the actual login via the API client.
    export async function handleAuthLogin(args: { username: string; password: string }): Promise<string> {
      try {
        const tokenData = await login(args.username, args.password);
        return JSON.stringify({
          success: true,
          message: "Login successful",
          expiresIn: tokenData.expires_in,
          tokenType: tokenData.token_type,
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          error: error instanceof Error ? error.message : "Unknown error",
        });
      }
    }
  • The schema definition for the auth_login tool, specifying name, description, and input parameters.
    export const authLoginTool = {
      name: "auth_login",
      description: "Authenticate with Evaluar using username and password. Returns success status and masked token info.",
      inputSchema: {
        type: "object" as const,
        properties: {
          username: {
            type: "string",
            description: "Email address for Evaluar account",
          },
          password: {
            type: "string",
            description: "Password for Evaluar account",
          },
        },
        required: ["username", "password"],
      },
    };
Behavior3/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. It discloses the authentication method (username/password) and return value (success status and masked token info), which are useful behavioral traits. However, it lacks details on error handling, rate limits, session management, or security implications (e.g., token expiration).

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 highly concise and front-loaded, consisting of two sentences that directly state the tool's function and return value. Every word contributes essential information without redundancy or fluff, making it efficient for an agent to parse.

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 (authentication with credentials) and lack of annotations or output schema, the description is minimally complete. It covers the basic action and return but omits critical context like error cases, token usage, or integration with other tools (e.g., 'auth_refresh'). For a security-sensitive operation, more detail would be beneficial.

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 clear documentation for both parameters (username as email, password as password). The description adds no additional parameter semantics beyond what the schema provides, such as format constraints or validation rules. The baseline score of 3 reflects adequate coverage by the schema alone.

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 tool's purpose: 'Authenticate with Evaluar using username and password.' It specifies the action (authenticate), the target system (Evaluar), and the method (username/password). However, it doesn't explicitly differentiate from sibling tools like 'auth_refresh' which likely handles token renewal rather than initial authentication.

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 alternatives. It doesn't mention prerequisites (e.g., needing credentials), when not to use it (e.g., if already authenticated), or how it relates to sibling tools like 'auth_refresh'. The agent must infer usage context from the tool name 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/yarmijosp94/evaluar-mcp'

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