Log in to Evaluar with your username and password to start managing eTalent processes.
Login to Evaluar using username and password
| Name | Required | Description | Default |
|---|---|---|---|
| password | Yes | Your Evaluar password | |
| username | Yes | Your Evaluar username (email) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It states the basic action but does not disclose important behavioral traits such as session creation, token generation, failure behavior, or side effects. An agent is left without information about what happens after successful authentication.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no unnecessary words. It earns its place but offers no additional structural aids such as usage notes or context that could improve the definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description is too thin. It does not explain what the agent can expect as a result (e.g., token or session) or how this login fits into the wider workflow among sibling tools. This leaves critical context missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 both parameters. The description adds no additional meaning beyond mentioning 'username and password,' which does not exceed what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Login') with a specific resource ('Evaluar') and the authentication method ('username and password'). It is easily distinguishable from sibling auth_refresh, which implies a different operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus auth_refresh, or about preconditions such as needing to log in before accessing other tools. The intended usage context must be inferred by the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.