Lists your elempleo job applications with current statuses such as in process, expired, or deleted so you can track each application.
Lista tus postulaciones en elempleo con su estado (en proceso, vencida, eliminada…).
| Name | Required | Description | Default |
|---|---|---|---|
| pagina | No | ||
| por_pagina | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral context. It discloses the status categories returned (en proceso, vencida, eliminada), but does not state authentication requirements, pagination behavior, or how results are scoped beyond the possessive 'tus'.
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 definition is a single front-loaded sentence with zero waste. It states the core action and returned statuses efficiently.
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 simple read-only list tool with no output schema, the description states the resource and status values adequately. However, it omits parameter semantics and any annotation-level behavioral context, leaving notable gaps for an agent to infer.
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 0%, and the description never mentions the 'pagina' or 'por_pagina' parameters. It does not explain pagination or the allowed page-size options (20, 50, 100), so it fails to compensate for the undocumented parameters.
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 states a specific verb ('Lista') and resource ('tus postulaciones') in the elempleo context, and names returned status categories. It clearly identifies what the tool does, though it does not explicitly contrast itself with related siblings such as preguntas-de-postulacion or buscar-ofertas.
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?
The description gives no when-to-use conditions, prerequisites, or alternatives. It only implies viewing one's own applications, leaving the agent to infer when this tool should be chosen over sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.