Skip to main content
Glama

Cursos gratis en español

Rutas para aprender desde cero

rutas_de_aprendizaje
Read-onlyIdempotent

Guías paso a paso que ordenan cursos gratis en etapas (programación, datos, diseño, marketing, inglés, Excel…). Step-by-step learning paths built from free Spanish courses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and a closed-world scope, so the safety profile is covered. The description adds a content boundary — that the paths are built from free Spanish-language courses — which is behaviorally useful scope information, but it says nothing about return shape, path length, or what a 'stage' contains.

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 with the core idea front-loaded and the domain examples in parentheses doing useful disambiguation work. The Spanish and English sentences are near-duplicates, which is mild redundancy but acceptable for a bilingual catalog.

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 zero-parameter, read-only catalog tool with no output schema and full annotation coverage, the description supplies enough for an agent to decide to call it. Only the absence of any guidance on choosing between it and the sibling course tools keeps it from a 5.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies a no-argument catalog call, and there are no parameter semantics left for it to explain.

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 names a specific resource — step-by-step learning paths that sequence free courses into stages — and lists concrete domains (programming, data, design, marketing, English, Excel). That is far more specific than the bare title, and the concept of a 'path' is distinguishable from the sibling course-lookup tools. It stops short of explicitly stating how it differs from buscar_cursos or mejores_cursos.

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: an agent can infer this is for when a user wants a structured curriculum rather than a single course. There is no explicit 'use this when...' statement and no mention of when to prefer buscar_cursos or mejores_cursos instead.

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