Skip to main content
Glama

get_course_thread

Retrieve a specific discussion thread from an Ed Discussion course using its course ID and thread number.

Instructions

Get a thread by its course-local number (the # shown in the Ed UI)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_idYesCourse ID
thread_numberYesThread number within the course

Implementation Reference

  • The API implementation that performs the actual network request for getting a course thread.
    async getCourseThread(
      courseId: number,
      threadNumber: number
    ): Promise<EdGetThreadResponse> {
      return this.request<EdGetThreadResponse>(
        "GET",
        `courses/${courseId}/threads/${threadNumber}`
      );
    }
  • src/index.ts:154-167 (registration)
    The MCP tool registration and handler wrapper for get_course_thread.
    server.tool(
      "get_course_thread",
      "Get a thread by its course-local number (the # shown in the Ed UI)",
      {
        course_id: z.number().describe("Course ID"),
        thread_number: z.number().describe("Thread number within the course"),
      },
      async ({ course_id, thread_number }) => {
        try {
          return ok(await api.getCourseThread(course_id, thread_number));
        } catch (err) {
          return fail(err);
        }
      }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the addressing behavior (course-local vs. global IDs) which is crucial, but lacks information on error handling (what if thread_number doesn't exist?), return format, or rate limiting.

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?

Single sentence with zero waste. The information is front-loaded with the action verb, and the parenthetical efficiently adds UI context without verbosity.

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

Completeness4/5

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

Given the tool's simplicity (2 parameters, 100% schema coverage) and the presence of a similar sibling tool, the description adequately covers the selection-critical distinction (course-local numbering). Minor gap: no mention of return structure or 404 behavior, though this is somewhat mitigated by the straightforward 'Get' operation type.

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?

While the schema has 100% description coverage (baseline 3), the description adds valuable semantic context that 'thread_number' corresponds to 'the # shown in the Ed UI'—providing UI mapping context not present in the structured schema.

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?

The description uses a specific verb ('Get') + resource ('thread') and clearly distinguishes this tool from sibling 'get_thread' by specifying the unique addressing scheme ('course-local number'). This specificity prevents selection errors between the two retrieval options.

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?

The parenthetical '(the # shown in the Ed UI)' provides clear contextual guidance on when to use this tool (when referencing UI-visible numbers). However, it could explicitly contrast with 'get_thread' to clarify when to use each retrieval method.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rob-9/edstem-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server