Skip to main content
Glama

star_thread

Bookmark important discussion threads for quick access and future reference in Ed Discussion courses.

Instructions

Star/bookmark a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID

Implementation Reference

  • Implementation of the starThread API call.
    async starThread(threadId: number): Promise<void> {
      await this.request("POST", `threads/${threadId}/star`);
    }
  • src/index.ts:300-312 (registration)
    Registration logic for the star_thread tool using server.tool.
    server.tool(
      `${action}_thread`,
      threadActionDescs[action],
      { thread_id: z.number().describe("Global thread ID") },
      async ({ thread_id }) => {
        try {
          await threadActions[action].call(api, thread_id);
          return msg(`Thread ${thread_id} ${action}ed successfully.`);
        } catch (err) {
          return fail(err);
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full disclosure burden. While 'star/bookmark' implies a state mutation, the description lacks critical safety context: reversibility (via unstar_thread), idempotency, permission requirements, or failure modes. For a write operation with zero annotation coverage, this is insufficient.

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?

Extremely efficient at three words with zero redundancy. However, given the absence of annotations and behavioral details, the description is arguably too terse rather than appropriately sized. The structure itself is sound with the action front-loaded.

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?

Inadequate for a state-mutating tool with no output schema and no annotations. The description omits the existence of the direct inverse operation (unstar_thread), does not clarify the persistence of the bookmark, and lacks error context. A minimal viable description for this mutation should mention reversibility.

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 100% ('Global thread ID'), so the schema fully documents the parameter. The description adds no supplemental context about the ID format, where to obtain it, or examples, but baseline 3 is appropriate when the schema is self-sufficient.

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?

Uses specific verbs ('Star/bookmark') and identifies the resource ('thread'), making the core action clear. However, it fails to differentiate from sibling tool 'pin_thread' (which typically makes content prominent for all users vs. personal bookmarking) or indicate this is the inverse of 'unstar_thread'.

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?

Provides no guidance on when to use this tool versus alternatives like 'pin_thread' for prominent display. Does not mention that 'unstar_thread' reverses this action or whether starring is idempotent. No prerequisites or conditions are specified.

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