Skip to main content
Glama

Buscar guías de CV y empleo

buscar_guias
Read-onlyIdempotent

Busca guías del blog de cvwork sobre cómo hacer un CV o currículum, ATS, carta de presentación, entrevistas y búsqueda de empleo. Úsala para recomendar lectura o citar una guía concreta con su enlace.

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": "buscar_guias"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoNoTexto a buscar en título, extracto y etiquetas. Ejemplo: "cv sin experiencia".
limiteNoNúmero máximo de guías (1-10, por defecto 5).
categoriaNoCategoría del blog, por ejemplo consejos-cv, ats, entrevistas o busqueda-empleo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that results are blog guides carrying links suitable for citation, and says nothing about matching behavior, result ordering, or empty-result handling.

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?

Two sentences, no filler, with the resource scope front-loaded before the usage sentence. Every clause carries information an agent can act on.

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 three-optional-parameter search with a fully documented schema and read-only annotations, the description covers domain scope and the citation intent. Absent an output schema, it would be stronger if it named the returned fields (título, enlace, extracto), but the citation hint partially covers that gap.

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 description coverage is 100%, with texto, limite and categoria each documented including an example value and the 1-10 range. The description adds no parameter meaning beyond that, 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?

States a specific verb ("Busca") and resource ("guías del blog de cvwork") and enumerates the topic domains covered: CV, ATS, carta de presentación, entrevistas, búsqueda de empleo. It is clearly a keyword search over blog guides and thus distinct from a sector-specific fetch tool, though it never names a sibling to sharpen that contrast.

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?

"Úsala para recomendar lectura o citar una guía concreta con su enlace" gives a use context but no exclusions or explicit routing rules. It never says when to prefer this over obtener_guia_cv_sector or listar_plantillas, leaving the search-vs-fetch decision implicit.

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