Skip to main content
Glama

courses_get

Read-only

Read one course: details, price, outline with lesson status, and optionally learner progress.

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": {
      "workspace": "<workspace>",
      "course_id": "<course_id>"
    },
    "name": "courses_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
workspaceYes
include_learnersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, non-destructive and closed-world, so the safety profile is covered. The description adds useful context beyond that by enumerating the payload shape (price, outline, lesson status) and flagging that learner progress is optional. It says nothing about behavior for missing or unauthorized course IDs.

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?

A single front-loaded sentence with the returned content listed in order of importance and no filler. It is arguably too terse for a 0%-documented parameter set, but nothing is wasted or buried.

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

Completeness3/5

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

As a read-only single-entity getter with no output schema, the description adequately covers what comes back and that one field is conditional. The remaining gaps are the two undocumented required parameters and the absence of any failure-mode note, which matter given zero schema prose.

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 0%, so the description must carry parameter meaning. It only indirectly explains include_learners via 'optionally learner progress'; workspace scoping and the crs_ ID format are left entirely to the schema, which supplies only a regex pattern and no prose.

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 verb and resource ('Read one course') and enumerates the returned content (details, price, outline with lesson status, learner progress), which distinguishes it from the sibling courses_list. It stops short of explicitly contrasting itself with that list tool, so it is clear but not sibling-routing.

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?

Single-course retrieval is implied by 'Read one course', and 'optionally learner progress' hints at when to set include_learners. There is no explicit when-not guidance, no mention of how to locate the course_id, and no statement that courses_list should be used first to discover IDs.

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