devto-mcp

Get article comments

devto_get_comments

Retrieve threaded comments for a Dev.to article by supplying its article ID.

Instructions

Get the threaded comments for an article.

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": {
      "articleId": "<articleId>"
    },
    "name": "devto_get_comments"
  }
}

Input Schema

Name	Required	Description	Default
`articleId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It indicates the result (threaded comments) but does not explain authentication requirements, pagination, error behavior, or read-only nature beyond the verb 'get'. This is insufficient for full transparency.

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?

The description is a single short sentence, front-loaded with the key action, and contains no redundant or filler content. Every word earns its place.

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?

Despite low complexity (one parameter), the description lacks essential context: no output format, response structure, or error handling. Since there is no output schema and no annotations, the description should provide at least a basic expectation of what the tool returns, which it does only vaguely with 'threaded comments'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does not provide any additional meaning for 'articleId'—no format, examples, or source for the ID. The phrase 'for an article' only repeats the parameter name.

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 ('Get') and resource ('threaded comments for an article'), clearly distinguishing it from sibling tools like devto_get_article or devto_list_articles. The term 'threaded' adds specificity.

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?

No guidance is provided on when to use this tool versus alternatives. There are no explicit use cases, prerequisites, or exclusions. The description simply states the action without contextualizing it among the sibling tools.

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

Deploy Server