Skip to main content
Glama

Get course

get_course
Read-onlyIdempotent

One course in full: who it is for, learning outcomes, agenda by day, what is included, exam, prerequisites, trainers, FAQ, price, upcoming dates and the registration url. Call it as soon as someone asks anything about a specific course.

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": {
      "slug": "<slug>"
    },
    "name": "get_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en
slugYesThe slug as another tool returned it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description contributes the return payload composition, which matters because no output schema exists, and it implies slug-based lookup of one known entity. It does not cover behavior on an unknown slug or the effect of the lang parameter on returned content.

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?

Two sentences, zero filler: the resource is front-loaded and every clause in the list earns its place by naming a returned field. The trigger sentence closes with the call condition rather than burying it.

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?

With no output schema, the description carries the burden of describing return content and does so exhaustively, including nested sections like agenda by day and trainers. Combined with the annotated read-only profile and fully documented two-parameter schema, an agent has everything needed to select and call it.

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 100%: slug is documented as coming from another tool's output and lang carries an enum plus default. The description adds no further detail on either parameter, so the 3 baseline applies.

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?

"One course in full" plus an enumeration of exactly what the record contains (outcomes, agenda by day, exam, prerequisites, trainers, FAQ, price, dates, registration url) makes the resource and payload unambiguous. It does not name the sibling search tool, so differentiation from search_courses is only implied by the phrase "a specific course".

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

Usage Guidelines4/5

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

"Call it as soon as someone asks anything about a specific course" is an explicit, actionable trigger that clarifies the intended entry point. It stops short of stating exclusions or pointing to search_courses/list_* tools when the course identity is not yet known.

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