Skip to main content
Glama

Course Topics

course_topics
Read-only

Fetch the topic list for a given course ID so agents can review course content and plan assessments.

Instructions

Temas (topics) de un curso.

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_id": "<course_id>"
    },
    "name": "course_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

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?

The readOnlyHint annotation already tells the agent this is a safe read, so the description's job is to add context about the result or constraints. It adds nothing: no mention of pagination, ordering, whether the course must exist, or what an empty result means. It does not contradict the annotation, but it is pure restatement.

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?

The single short sentence contains no filler, but its brevity reflects under-specification rather than discipline. There is nothing front-loaded beyond the resource name because there is nothing else.

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 return values need not be spelled out, and the annotation covers the safety profile. Even so, a course-scoped read tool with one undocumented parameter should say what the course_id identifies and roughly what scope of topics is returned; neither is present.

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 with 0% schema description coverage, so the description carries the full burden of explaining course_id. It does not mention the parameter at all — not its meaning, format, or whether it refers to a course identifier the caller must already hold.

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 description names a specific resource (topics) scoped to a course, which is more than a bare restatement of the name. But it is a noun phrase with no verb, so it never says whether it lists, counts, or retrieves topics, and it does not differentiate itself from siblings like list_courses or get_tag.

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 at all: no indication of prerequisites, when a caller would want course topics rather than course_results or course_access, or what to do if the course has no topics. The agent must infer the call site entirely from the name.

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