Skip to main content
Glama

accept_answer

Mark a comment as the accepted solution to resolve a question thread in Ed Discussion.

Instructions

Accept a comment as the answer to a question thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thread_idYesGlobal thread ID
comment_idYesComment ID to accept

Implementation Reference

  • The actual API implementation for accepting an answer.
    async acceptAnswer(threadId: number, commentId: number): Promise<void> {
      await this.request("POST", `threads/${threadId}/accept/${commentId}`);
    }
  • src/index.ts:390-404 (registration)
    Tool registration and handler invocation for 'accept_answer'.
    server.tool(
      "accept_answer",
      "Accept a comment as the answer to a question thread",
      {
        thread_id: z.number().describe("Global thread ID"),
        comment_id: z.number().describe("Comment ID to accept"),
      },
      async ({ thread_id, comment_id }) => {
        try {
          await api.acceptAnswer(thread_id, comment_id);
          return msg(`Comment ${comment_id} accepted as answer for thread ${thread_id}.`);
        } catch (err) {
          return fail(err);
        }
      }
Behavior2/5

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

With no annotations provided, the description fails to disclose mutation side effects: it does not state whether acceptance is reversible, if it notifies the comment author, locks the thread, or replaces any previously accepted answer. Critical behavioral context for a state-changing operation is missing.

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 of nine words with zero redundancy. Information is front-loaded and every word earns its place regarding the core action.

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

Completeness3/5

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

For a two-parameter mutation tool without annotations or output schema, the description meets minimum viability but leaves significant gaps regarding authorization scope, permanence of the action, and side effects that would help an agent invoke this safely.

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% (both thread_id and comment_id are documented), so the baseline is adequate. The description does not add syntax details, validation rules, or semantic relationships between parameters beyond what the schema already provides.

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 ('Accept') with clear resources ('comment' as 'answer' to 'question thread'), and distinguishes the Q&A workflow from sibling endorsement tools by specifying this marks the resolution to a question.

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?

While the description implies use when marking a solution, it lacks explicit guidance on prerequisites (e.g., thread ownership requirements), when to prefer this over endorse_comment, or whether this action is reversible (no unaccept_answer sibling exists).

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