Skip to main content
Glama

get_course_tools

Retrieve which modules a course has enabled—documents, assignments, exercises, forums—to identify available course tools before accessing them.

Instructions

Which modules (documents, assignments, exercises, forum...) a course has enabled.

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": {
      "course": "<course>"
    },
    "name": "get_course_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. The word 'enabled' usefully implies a read-only inspection of configuration rather than content, but the description says nothing about whether disabled modules are omitted, whether the caller needs enrollment or teacher rights, or how the categories are represented.

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?

It is a single short fragment with no wasted words, which is good, but the economy comes at the cost of a complete sentence and a clear leading verb. It reads as an abbreviated note rather than a front-loaded statement of what the tool returns.

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

Completeness2/5

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

An output schema exists, so the return shape need not be described. Still, for a tool with no annotations and an undocumented required parameter, the description omits the two things an agent most needs: the accepted form of the course identifier and the fact that this is a safe read operation.

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?

There is one required parameter ('course') with 0% schema description coverage, so the description must compensate for the gap. It only says 'a course' and never clarifies whether the value is a course ID, a short name, or a display name — a format ambiguity that matters given list_courses exists as a prerequisite lookup.

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

Purpose3/5

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

The phrase 'Which modules (documents, assignments, exercises, forum...) a course has enabled' names a specific resource and even enumerates the module categories, so the agent can infer it is a discovery/read tool for a course's enabled features. However, it is a noun fragment with no verb, so the action (query vs. configure) must be inferred, and no sibling such as list_courses or get_announcements is referenced to sharpen the boundary.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite stated (e.g. must the course be visible to the caller), and no indication of how this relates to the many sibling get_*/list_* tools. The only implied usage — 'find out what a course exposes' — is left entirely to inference.

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