Skip to main content
Glama

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

Ver las tareas tipo de una profesión

tareas_de_una_profesion
Read-onlyIdempotent

Devuelve las tareas típicas de una profesión según las tablas de Reinventa, las mismas que ofrece la evaluación de la web: cada una con su «id», categoría (Vulnerable, Aumentable o Resiliente, con su explicación), puntuación de partida de 0 a 100 (más baja, más expuesta a la IA), horizonte estimado, razón y recomendación. Con «sector» se añaden las 3 tareas de ese sector. Sirve para enseñar el mapa de tareas de una profesión y para elegir, por «id», las que se pasan a evaluar_tareas. Si la profesión no está en las tablas, devuelve las tareas del sector y las genéricas y lo dice. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profesion": "<profesion>"
    },
    "name": "tareas_de_una_profesion"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorNoOpcional. Sector, por id o por nombre: banca (Banca y finanzas), salud (Salud), legal (Legal), retail (Comercio), industria (Industria), tecnologia (Tecnología), educacion (Educación), construccion (Construcción), logistica (Logística), marketing (Marketing), administracion (Administración). Sin él se usa el habitual de la profesión.
profesionYesNombre de la profesión (p. ej. «Contable», «abogada», «jefe de proyecto»).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the degraded result when the profession is unknown (sector + generic tasks, and it says so), the dual output shape (Spanish prose plus structuredContent starting with «url»), and the requirement to cite the source and avoid job advice. These are operational details an agent cannot infer from structured fields.

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

Conciseness4/5

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

Front-loaded with what is returned, then usage, fallback, output contract and disclaimers; nearly every clause carries information. It is delivered as one dense run-on block without paragraph breaks, which makes the source-citation and disclaimer rules easy to skim past.

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?

For a 2-parameter read-only lookup with no output schema, the description covers what is returned, the fallback case, the output contract (url in structuredContent), and the citation/disclaimer obligations. Nothing an agent needs in order to call it and report the result correctly appears to be missing.

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?

Schema coverage is 100%, so the baseline is 3; the description adds value beyond it by explaining that passing «sector» appends that sector's 3 tasks and that «id» is the handle used downstream. It does not spell out the profession-name matching/normalization behavior (accents, feminine forms), which the schema hints at only via examples.

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?

Opens with a specific verb+resource ("Devuelve las tareas típicas de una profesión") and enumerates exactly what each task contains (id, categoría, puntuación 0-100, horizonte, razón, recomendación). It also positions itself against the sibling evaluar_tareas by saying its ids are the ones that get passed there, so an agent can tell it apart without opening the schema.

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

Usage Guidelines4/5

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

States the two concrete uses: showing a profession's task map and selecting tasks by id to feed evaluar_tareas, which routes the agent to the correct sibling for evaluation. It also documents the fallback path when the profession isn't in the tables. It never says explicitly when NOT to use it (e.g. vs buscar_profesion or guia_de_profesion), so it stops short of a 5.

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