Skip to main content
Glama
yarmijosp94

Evaluar MCP Server

by yarmijosp94

auth_refresh

Refresh authentication tokens for the Evaluar recruitment platform to maintain continuous access when tokens approach expiration.

Instructions

Refresh the authentication token. Use this when the current token is about to expire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the logic for refreshing the authentication token.
    export async function handleAuthRefresh(): Promise<string> {
      try {
        const tokenData = await refreshToken();
        return JSON.stringify({
          success: true,
          message: "Token refreshed successfully",
          expiresIn: tokenData.expires_in,
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          error: error instanceof Error ? error.message : "Unknown error",
        });
      }
    }
  • The tool definition schema for "auth_refresh".
    export const authRefreshTool = {
      name: "auth_refresh",
      description: "Refresh the authentication token. Use this when the current token is about to expire.",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    };
  • src/index.ts:53-54 (registration)
    The registration and dispatching logic in the main index file for the "auth_refresh" tool.
    case "auth_refresh":
      result = await handleAuthRefresh();
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 of behavioral disclosure. It mentions the action ('Refresh') but lacks details on permissions, rate limits, or what happens on failure. However, it does add useful context about token expiration, which is valuable beyond a bare description.

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 sentences with zero waste: the first states the purpose, and the second provides usage guidelines. It is front-loaded and efficiently conveys all necessary information without redundancy or fluff.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is nearly complete for its purpose. It covers what the tool does and when to use it, though it could benefit from mentioning behavioral aspects like error handling or token persistence. The lack of output schema is not critical here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it implies the tool operates on an implicit token context, slightly enhancing understanding. Baseline is 4 for zero parameters.

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 ('Refresh') and resource ('authentication token'), distinguishing it from sibling tools like 'auth_login' which likely obtains a token initially. It precisely defines what the tool does without being vague or tautological.

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

Usage Guidelines5/5

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

The description explicitly provides when to use this tool ('when the current token is about to expire'), offering clear guidance on its context and distinguishing it from alternatives like 'auth_login' for initial authentication. This helps the agent select the correct tool based on token state.

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