Skip to main content
Glama

Free courses

mkh_free_courses
Read-onlyIdempotent

List free courses with optional category, level, rating, and sorting filters to help users find watchable courses without payment before checking details.

Instructions

List the free courses (final_price 0, about 740 of them), optionally in one category: hours, rating, students.

Free courses are watchable without paying, a certificate may still cost money. Next: mkh_course.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 = first.
levelNoCourse level.any
limitNoCourses per page.
sortingNopopular, new, rate = best rated, manual = site order.popular
min_ratingNoMinimum average rating.
category_slugNoCategory slug from mkh_categories, e.g. 'python' or 'programming'; '-' = every category.-

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the meaningful domain caveat that free viewing may still involve paid certificates, plus an approximate result count, but it omits pagination and return-shape behavior.

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?

The description is short and front-loads the key scope: free courses at final_price 0. The parenthetical about categories is awkward, but overall it avoids unnecessary length.

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 six-parameter listing tool with full schema coverage and read-only annotations, the description covers what is listed and clarifies what 'free' means. It does not describe return fields or pagination, but the schema handles parameters and there is no output schema to explain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already fully documented. The description's only parameter-like claim, 'optionally in one category: hours, rating, students', does not map to any schema parameter and risks misdirecting an agent rather than adding meaning.

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: list free courses with final_price 0, about 740 of them. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like mkh_cheapest or mkh_deals, and the 'category: hours, rating, students' phrase is confusing.

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?

The description gives useful context that free courses are watchable without paying while certificates may cost, and points to mkh_course as a next step. However, it does not say when to use this instead of mkh_cheapest or mkh_deals, nor does it state any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.