Skip to main content
Glama

get_thread

Retrieve an Ed Discussion thread by its global ID to access all comments and answers in one view.

Instructions

Get a thread by global ID, including all comments and answers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID

Implementation Reference

  • The core API handler method that performs the network request to fetch thread details.
    async getThread(threadId: number): Promise<EdGetThreadResponse> {
      return this.request<EdGetThreadResponse>("GET", `threads/${threadId}`);
    }
  • src/index.ts:139-150 (registration)
    The MCP tool registration for 'get_thread', which calls the api.getThread handler.
    server.tool(
      "get_thread",
      "Get a thread by global ID, including all comments and answers",
      {
        thread_id: z.number().describe("Global thread ID"),
      },
      async ({ thread_id }) => {
        try {
          return ok(await api.getThread(thread_id));
        } catch (err) {
          return fail(err);
        }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully discloses the scope of returned data ('including all comments and answers'), which compensates partially for the missing output schema, though it omits explicit read-only status or error behaviors.

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?

The description is a single, front-loaded sentence with zero redundancy. Every clause serves a distinct purpose: the action ('Get'), the identification method ('by global ID'), and the return payload scope ('including all comments and answers').

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?

For a simple single-parameter retrieval tool, the description is appropriately complete. It compensates for the lack of output schema by describing the returned content structure (comments and answers), though it could be improved by noting the singular vs. plural return nature or error handling.

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 coverage is 100%, establishing a baseline of 3. The description reinforces the parameter semantics by referencing 'global ID' in the narrative, but does not add syntax details, example values, or constraints beyond what the schema already documents.

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') and resource ('thread'), and explicitly scopes the operation with 'by global ID'—effectively distinguishing it from sibling tools like get_course_thread (course-scoped) and list_threads (plural listing).

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?

The phrase 'by global ID' provides implicit guidance on when to use this tool (when possessing a global identifier), but lacks explicit contrast with alternatives like get_course_thread or search_threads, and does not state prerequisites or exclusion criteria.

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