Skip to main content
Glama

endorse_comment

Mark a comment as endorsed by staff to highlight valuable contributions in Ed Discussion forums.

Instructions

Endorse a comment (staff)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesComment ID

Implementation Reference

  • The actual implementation of the endorse_comment tool logic in the API class.
    async endorseComment(commentId: number): Promise<void> {
      await this.request("POST", `comments/${commentId}/endorse`);
    }
  • src/index.ts:362-374 (registration)
    Registration of the endorse_comment MCP tool.
    server.tool(
      "endorse_comment",
      "Endorse a comment (staff)",
      { comment_id: z.number().describe("Comment ID") },
      async ({ comment_id }) => {
        try {
          await api.endorseComment(comment_id);
          return msg(`Comment ${comment_id} endorsed.`);
        } 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 full responsibility for behavioral disclosure but fails to explain what endorsement actually does (visibility changes, official marking, etc.), whether it is reversible (despite unendorse_comment existing), or specific authorization requirements beyond the cryptic '(staff)' label.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the four-word description is not verbose, it is arguably underspecified rather than optimally concise. The parenthetical '(staff)' appears without context, suggesting the description sacrifices necessary clarity for brevity.

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 tool with no annotations or output schema, the description is insufficient. It fails to explain the endorsement mechanism, the scope of staff privileges required, side effects, or the relationship to the unendorse operation.

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 for the single comment_id parameter. The description adds no additional semantic context, but with complete schema coverage, it meets the baseline expectation without needing compensation.

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 states the specific verb ('Endorse') and resource ('comment'), distinguishing it from sibling tools like endorse_thread and unendorse_comment. However, the parenthetical '(staff)' is ambiguous—it could indicate required permissions or a specific endorsement type—preventing a perfect score.

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 alternatives like endorse_thread, or when to use unendorse_comment instead. It does not clarify prerequisites implied by '(staff)' or explain endorsement workflows.

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