Skip to main content
Glama

unendorse_comment

Remove endorsement from a comment in Ed Discussion to retract support or correct previous approval.

Instructions

Remove endorsement from a comment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesComment ID

Implementation Reference

  • The actual implementation of the tool, which makes a POST request to the API to unendorse a comment.
    async unendorseComment(commentId: number): Promise<void> {
      await this.request("POST", `comments/${commentId}/unendorse`);
    }
  • src/index.ts:376-388 (registration)
    Registration of the "unendorse_comment" tool, mapping it to the API method.
    server.tool(
      "unendorse_comment",
      "Remove endorsement from a comment",
      { comment_id: z.number().describe("Comment ID") },
      async ({ comment_id }) => {
        try {
          await api.unendorseComment(comment_id);
          return msg(`Comment ${comment_id} unendorsed.`);
        } 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 carries the full burden of behavioral disclosure but fails to specify idempotency (what happens if the comment is already unendorsed?), authorization requirements, or side effects. It only states the action without explaining operational constraints or error conditions.

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?

The description is a single four-word sentence that is front-loaded and efficient. While it avoids verbosity, its extreme brevity contributes to under-specification; it earns its place but could accommodate one additional sentence of behavioral context without sacrificing clarity.

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?

For a mutation operation with no annotations and no output schema, the description is insufficient. It lacks critical context such as success/failure conditions, whether the operation is idempotent, and what state changes occur on the comment, which are necessary for an agent to invoke the tool 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?

The input schema has 100% description coverage (comment_id is documented as 'Comment ID'), establishing a baseline score. The description implies the comment_id parameter by mentioning 'a comment' but adds no semantic detail about the parameter's format, constraints, or relationship to the operation beyond what the schema already provides.

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?

The description clearly states the action (Remove) and target (endorsement from a comment), distinguishing it from sibling tools like unendorse_thread. However, it essentially restates the tool name with minor expansion ('unendorse' → 'Remove endorsement'), lacking domain-specific elaboration on what endorsement means in this context.

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?

The description provides no guidance on when to use this tool versus its sibling endorse_comment (the inverse operation), nor does it mention prerequisites such as whether the user must have previously endorsed the comment or have specific permissions to remove the endorsement.

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