Skip to main content
Glama

Guía de CV por sector

obtener_guia_cv_sector
Read-onlyIdempotent

Devuelve cómo hacer un CV (currículum, hoja de vida) para un sector: respuesta directa, puestos típicos con las palabras clave ATS que conviene usar, habilidades, matices en Latinoamérica y preguntas frecuentes. Úsala cuando el usuario pida un ejemplo o consejos de CV de logística, ingeniería, farmacia, administración, enfermería, tecnología, hostelería o comercial.

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": {
      "sector": "<sector>"
    },
    "name": "obtener_guia_cv_sector"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYesSector: logistica, ingenieria, farmacia, administracion, enfermeria, tecnologia, hosteleria o comercial.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false. Beyond that, the description usefully discloses the response contents, including ATS keywords, LatAm nuances, and FAQs, although it does not specify the output format or any limitations beyond the sector scope.

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 front-loaded with the purpose and then the usage trigger, with no filler. Each clause adds useful scope or content information, making it appropriately sized for a simple one-parameter tool.

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?

For a simple, read-only guide tool with one fully documented enum parameter and no output schema, the description is largely complete: it explains the use case and enumerates the sections returned. The main remaining gap is that the response format is not specified, so an agent knows the content but not the exact shape.

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?

There is one parameter with 100% schema description coverage, including the same enum values listed in the description. The description identifies the sector concept but adds no syntax, format, or selection meaning beyond what the schema already provides, so the baseline of 3 applies.

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?

The description uses a specific verb and resource: "Devuelve cómo hacer un CV ... para un sector", and enumerates what the response contains (puestos típicos, palabras clave ATS, habilidades, matices en Latinoamérica, preguntas frecuentes). It is clear about what the tool does, though it does not explicitly differentiate itself from siblings such as analizar_cv_ats or buscar_guias.

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?

It gives an explicit usage trigger: "Úsala cuando el usuario pida un ejemplo o consejos de CV" and lists the supported sectors. It does not state when not to use it or name an alternative tool for related tasks, so it falls short of full when/when-not guidance.

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