Skip to main content
Glama

Search courses

search_courses
Read-onlyIdempotent

Every published course, in catalogue order, or those matching a search (part of a name or a topic, e.g. "27001", "AI", "pentest"). Short records: slug, title, summary, level, format, duration, price, certificates, next date, url. Call get_course with the slug for anything specific.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so safety is covered. The description adds behavior beyond that: unfiltered results come back in catalogue order, results are deliberately short records, and the search matches partial name or topic rather than exact strings. It does not discuss result volume or truncation for large catalogues, which keeps it short of a 5.

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?

Three tight sentences, front-loaded with scope, then return shape, then the hand-off to the sibling. No filler and no repetition of schema or annotation content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description fills that gap by enumerating the record fields (slug, title, summary, level, format, duration, price, certificates, next date, url). Combined with the documented lang enum, an agent has everything needed to call and interpret this tool.

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 50% — lang is documented in the schema, but search has no schema description. The description compensates well by explaining that search accepts part of a name or a topic and by giving three concrete example queries. The lang parameter is left entirely to the schema, which is acceptable since the enum and default are self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and both modes precisely: the full published catalogue in catalogue order, or a filtered subset matching a partial name or topic. It explicitly names the sibling get_course as the drill-down alternative, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: use this for browsing or partial-string matching, and 'Call get_course with the slug for anything specific.' The boundary between list-level and detail-level access is stated rather than inferred.

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