Skip to main content
Glama

esa_get_comment

Retrieve a specific comment from esa using its ID to view details and related data like stargazers.

Instructions

Get a specific comment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesID of the comment to retrieve
includeNoレスポンスに含める関連データ (例: 'stargazers')

Implementation Reference

  • Tool schema definition for 'esa_get_comment', including name, description, and input schema with required 'comment_id'.
    const getCommentTool: Tool = {
      name: "esa_get_comment",
      description: "Get a specific comment",
      inputSchema: {
        type: "object",
        properties: {
          comment_id: {
            type: "number",
            description: "ID of the comment to retrieve",
          },
          include: {
            type: "string",
            description: "レスポンスに含める関連データ (例: 'stargazers')",
          },
        },
        required: ["comment_id"],
      },
    };
  • Handler logic in the CallToolRequest switch statement: validates args, calls esaClient.getComment, and returns JSON response.
    case "esa_get_comment": {
      const args = request.params.arguments as unknown as GetCommentArgs;
      if (!args.comment_id) {
        throw new Error("comment_id is required");
      }
      const response = await esaClient.getComment(args.comment_id, args.include);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • EsaClient.getComment method: constructs API URL for /comments/{comment_id}, appends include param if provided, fetches and returns JSON.
    async getComment(comment_id: number, include?: string): Promise<any> {
      const params = new URLSearchParams();
      
      if (include) params.append("include", include);
    
      const url = `${this.baseUrl}/comments/${comment_id}${params.toString() ? `?${params}` : ""}`;
      const response = await fetch(url, { headers: this.headers });
    
      return response.json();
    }
  • index.ts:607-617 (registration)
    Registration of 'esa_get_comment' tool (as getCommentTool) in the tools list returned by ListToolsRequest handler.
    tools: [
      listPostsTool,
      getPostTool,
      createPostTool,
      updatePostTool,
      listCommentsTool,
      getCommentTool,
      createCommentTool,
      getMembersTool,
      getMemberTool,
    ],
  • TypeScript interface defining arguments for esa_get_comment tool.
    interface GetCommentArgs {
      comment_id: number;
      include?: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get a specific comment' implies a read-only operation, but it does not specify authentication requirements, rate limits, error handling, or response format. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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 very concise with a single sentence, 'Get a specific comment', which is front-loaded and wastes no words. However, it is overly brief, bordering on under-specification, as it could benefit from slightly more detail without losing efficiency. It earns a high score for conciseness but loses a point for being too minimal.

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?

Given the tool's complexity (2 parameters, no output schema, no annotations), the description is incomplete. It does not explain what 'Get' returns (e.g., comment details), how to handle the 'include' parameter effectively, or any behavioral aspects like permissions. For a read operation with undocumented outputs, more context is needed to make it fully usable.

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, with clear documentation for 'comment_id' and 'include'. The description adds no additional meaning beyond the schema, such as examples for the 'include' parameter or context on comment IDs. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get a specific comment' clearly states the verb ('Get') and resource ('comment'), making the purpose understandable. However, it lacks specificity about what 'Get' entails (e.g., retrieving details) and does not differentiate from sibling tools like 'esa_list_comments' or 'esa_get_post', which handle similar resources. This makes it vague compared to more detailed alternatives.

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. It does not mention sibling tools like 'esa_list_comments' for listing multiple comments or 'esa_get_post' for retrieving posts, nor does it specify prerequisites or exclusions. Without such context, users must infer usage from the tool name alone.

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/kajirita2002/esa-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server