Skip to main content
Glama
Sign In
esa MCP Server

esa MCP Server

Official
by esaio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get a specific comment

esa_get_comment
Read-only

Fetch a specific esa.io comment by comment ID, optionally including stargazers. Use it to inspect one comment's details for review, reporting, or follow-up.

Instructions

Retrieves a specific comment by comment ID, with optional stargazers included.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "commentId": "<commentId>"
    },
    "name": "esa_get_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoSpecify 'stargazers' to include stargazers in the response
teamNameNoTeam name (required). Use esa_get_teams first to see available teams.
commentIdYesThe comment ID to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.13.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the optional stargazers inclusion, which is already documented in the schema, and says nothing about errors for missing IDs or the team-scoping requirement.

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?

A single front-loaded sentence with no filler; the lookup key and the optional expansion are both stated immediately. Nothing is wasted and nothing important is buried.

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

Completeness4/5

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

For a simple 3-parameter read with full schema coverage, no output schema, and clear annotations, the description covers the essentials. A note on the required team scoping or the single-comment vs list distinction would make it fully complete.

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%, so all three parameters (commentId, include, teamName) are already documented, including the enum guidance and the teamName prerequisite. The description restates commentId and the stargazers option without adding format or constraint detail, so baseline 3 applies.

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?

States a specific verb and resource ('Retrieves a specific comment') plus the lookup key ('by comment ID'), which distinguishes it from list-style siblings like esa_get_post_comments or esa_get_team_comments. It does not name those siblings explicitly, so it stops short of a 5.

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?

The phrase 'by comment ID' implies you need a known ID, which is usable context, but there is no explicit statement of when to use this versus the comment-listing siblings or the create/update/delete comment tools. Usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools