Skip to main content
Glama

Cursos gratis en español

Buscar cursos gratis

buscar_cursos
Read-onlyIdempotent

Busca cursos gratis en español por tema (p. ej. 'python', 'excel avanzado', 'inglés B1'). Devuelve título, autor, plataforma, duración, nivel, resumen y la URL de la ficha en cursosgratis.pro. Search free Spanish-language courses by topic.

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": {
      "query": "<query>"
    },
    "name": "buscar_cursos"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNoMáximo de resultados (1–10, 5 por defecto)
queryYesTema o palabras clave / topic or keywords
categoryNoSlug de categoría: programming, data-ai, design, marketing…
platformNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "youtube",
      -  "udemy",
      -  "mslearn"
      -]New value: +[
      +  "youtube",
      +  "udemy",
      +  "mslearn",
      +  "platzi",
      +  "netacad",
      +  "skillshop"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "youtube",
      -  "udemy"
      -]New value: +[
      +  "youtube",
      +  "udemy",
      +  "mslearn"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds value by listing the exact returned fields (título, autor, plataforma, duración, nivel, resumen, URL), which matters because there is no output schema. It does not disclose result capping or ranking behavior beyond what the schema already states.

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?

Two short sentences, front-loaded with the purpose and then the return payload, with no filler. The English translation duplicates the Spanish sentence, which is mild redundancy but justified for a bilingual tool name and description.

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?

Since no output schema exists, enumerating the returned fields fills a real gap and is the most useful part of the definition. Parameter behavior for filters (level, platform, category) is left to the schema, which is acceptable at 60% coverage but leaves some room.

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 60%, so most parameters are already documented in the schema. The description adds meaning only for 'query' via example topics; level, limit, category and platform get no additional explanation. Baseline 3 is appropriate given the schema does the heavy lifting.

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 with scope: 'Busca cursos gratis en español por tema', giving concrete query examples ('python', 'excel avanzado', 'inglés B1'). An agent can tell this is a topic search over free Spanish courses, though it stops short of naming how it differs from siblings like mejores_cursos or rutas_de_aprendizaje.

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 only implied by 'por tema' and the example keywords; there is no explicit statement of when to pick this over mejores_cursos or rutas_de_aprendizaje. An agent can infer it is the general search entry point, but the routing decision is left to inference.

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