Skip to main content
Glama

Cursos gratis en español

Ranking de los mejores cursos gratis

mejores_cursos
Read-onlyIdempotent

Ranking de los mejores cursos gratis en español de una herramienta (Excel, Python, SQL y bases de datos, Power BI, AutoCAD, Revit, SketchUp, Canva, inglés…), con la URL del ranking completo. Best free Spanish courses for a given tool.

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": {
      "topic": "<topic>"
    },
    "name": "mejores_cursos"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesHerramienta / tool, p. ej. 'Excel'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so safety and determinism are covered structurally. The description adds genuinely new behavioral content — that results are curated/ranked, restricted to free Spanish courses, and accompanied by a full-ranking URL. It does not say how many items come back or whether the URL is always present, so with annotations carrying the safety profile a 3 fits.

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

Conciseness3/5

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

The core Spanish sentence is front-loaded and informative, but it is then restated almost verbatim in an English one-liner, and the long parenthetical tool list repeats information that also serves the parameter. Slightly redundant, though nothing is sprawling or off-topic.

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 one-parameter, read-only, non-open-world tool with no output schema, the definition gives enough: what is returned (a ranking), the inclusion criterion (free, Spanish), and an extra artifact (the ranking URL). An agent could invoke it correctly without more, missing only result-size or pagination expectations.

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% and the schema already documents the single 'topic' parameter, so the baseline is 3. The description earns above baseline by enumerating concrete valid values (Excel, Python, SQL y bases de datos, Power BI, AutoCAD, Revit, SketchUp, Canva, inglés…), which tells the agent the parameter expects a tool/language name rather than a free-form query.

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 resource — a ranking of the best free Spanish-language courses for a given tool — plus the notable detail that the response includes the URL of the full ranking. The 'ranking' framing implicitly separates it from buscar_cursos (search) and rutas_de_aprendizaje (learning paths), but it never names or contrasts those siblings explicitly.

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 it should call this when it wants a curated best-of list rather than a search. There is no explicit when-to-use, when-not-to-use, or pointer to the sibling tools for the adjacent cases.

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