Skip to main content
Glama

Devto

by io.github.pipeworx-io

Get Article

get_article
Read-onlyIdempotent

Fetch full article content from DEV.to by ID (e.g., "12345"). Returns title, author, markdown body, tags, reactions, comments, and published date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric article ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesArticle numeric ID
urlYesArticle URL
tagsYesList of tags associated with article
titleYesArticle title
authorYesArticle author information
commentsYesCount of comments
reactionsYesCount of public reactions
descriptionYesArticle description or excerpt
organizationYesPublishing organization information
published_atYesPublication timestamp (ISO 8601 format)
body_markdownYesFull article content in markdown format
reading_time_minutesYesEstimated reading time in minutes

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds return fields (title, author, etc.) and source (DEV.to), providing useful context beyond annotations.

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?

Two sentences, front-loaded with purpose, no redundant phrases. Every word earns its place.

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?

Simple tool with rich annotations and output schema. Description covers purpose, input, and output appropriately, though it could mention missing details like authentication or error responses.

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

Parameters4/5

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

Schema coverage is 100% with a clear description. Description reinforces with example ('12345') and clarifies the ID is numeric, adding marginal value over schema alone.

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?

Clear verb ('Fetch'), resource ('full article content'), and identifier ('by ID'). Differentiates from siblings like get_articles (list) and search_articles (search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies use when article ID is known, but lacks explicit when-not-to-use or alternative tools. Context from sibling names helps, but no direct guidance.

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

All Devto toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes with clear descriptions, but some overlap exists, e.g., ask_pipeworx vs ask_pipeworx_grounded, and several entity/company tools that could be confused. Overall, well-described and mostly disambiguated.

Naming Consistency5/5

Tool names follow consistent patterns: snake_case, with clear prefixes for each group (e.g., polymarket_*, pipeworx_*, get_article, etc.). Naming is predictable and systematic, making it easy to understand the tool's domain and action.

Tool Count2/5

33 tools is high for a server named 'Devto', where only a few tools actually relate to DEV.to. The majority are for Pipeworx data and Polymarket, which are unrelated. The tool count feels bloated and misaligned with the server's apparent primary purpose.

Completeness2/5

For the DEV.to domain, coverage is incomplete: lacks create/update/delete for articles and missing user profile management. The Pipeworx and Polymarket tools are extensive, but that doesn't compensate for the gaps in the core feature set implied by the server name.

Resources