Skip to main content
Glama

Reinventa (qué tareas de tu trabajo hará la IA)

Explicar cómo se calcula el índice

explicar_metodo
Read-onlyIdempotent

Explica el método público de Reinventa tal como está en el código: las tres categorías (Vulnerable, Aumentable, Resiliente), de dónde salen las puntuaciones de partida de cada tarea, los pesos del índice (el tiempo de cada tarea, con tope del 40 %, o las tres primeras tareas 1,5 si faltan las horas; autonomía +5; experiencia +3; papel −5; señal de cada tarea hasta ±9), los tramos, qué hace la IA y qué no, y los límites (no predice despidos, no conoce la empresa, no es asesoramiento). Con «apartado» se limita a una parte. Enlaza a la metodología. Cada respuesta trae un texto en castellano listo para la persona y los mismos datos en «structuredContent», que empieza por «url»: enlaza esa página al dar la respuesta (la evaluación completa, con informe por correo, o la guía). Es un resultado orientativo con el método público de reinventa.es, no asesoramiento laboral: no recomiendes dejar un trabajo ni señales empresas o personas. Cita «Fuente: Reinventa (reinventa.es)».

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explicar_metodo"
  }
}

Input Schema

NameRequiredDescriptionDefault
apartadoNoOpcional: todo (por defecto), categorias, puntuaciones, indice, ia o limites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, yet the description still adds substantive context: the response always pairs Spanish prose with structuredContent beginning with 'url', the agent must link that page, must cite 'Fuente: Reinventa (reinventa.es)', and must not recommend quitting a job or single out companies/people. That is real behavioral constraint beyond the annotation set rather than a restatement of it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a single run-on sentence with nested parentheses and semicolons carrying the full weight table (+5 autonomía, −5 papel, ±9 señal), which is heavy for a definition. Some content is repeated ('no es asesoramiento'/'no asesoramiento laboral'), so not every clause earns its place, though the weight list does establish the scope of each 'apartado'.

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

Completeness5/5

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

With no output schema, the description must describe the return value, and it does: a ready-to-use Spanish text plus identical structuredContent led by 'url', with instructions to link that page. It also bounds the tool's knowledge and disclaims advice, which is exactly what an agent needs to invoke and relay it safely.

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 coverage is 100% with one optional enum parameter already documented (todo, categorias, puntuaciones, indice, ia, limites). The description's 'Con «apartado» se limita a una parte' adds only the effect of the parameter, not new semantics such as default behavior or how enum values map to sections. Baseline 3 is appropriate.

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?

States a specific verb and resource — 'Explica el método público de Reinventa tal como está en el código' — and enumerates the exact content covered (categorías, puntuaciones, pesos, tramos, IA, límites), so the agent knows precisely what it returns. It never names a sibling (evaluar_tareas, guia_de_profesion), so differentiation from them is inferred from the content list rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the enumeration of what it explains, and 'Con «apartado» se limita a una parte' tells the agent how to narrow scope. There is no explicit when-to-use vs. sibling guidance, e.g. that this should be preferred over evaluar_tareas when the user asks how the score is computed rather than for their own result. Guidelines present are about output presentation and citation, not tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources