Skip to main content
Glama

Devto

by io.github.pipeworx-io

Get Articles

get_articles
Read-onlyIdempotent

Get trending or recent DEV.to articles, optionally filtered by tag (e.g., "javascript", "react"). Returns title, author, reaction count, comments, reading time, and URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter articles by tag (e.g., "javascript", "python", "webdev")
topNoReturn top articles from the last N days (e.g., 7 for last week)
limitNoNumber of articles to return (default 10, max 30)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
articlesYesList of article summaries

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so description doesn't need to restate safety. Adds value by specifying return fields (title, author, reaction count, etc.) and that results are trending/recent.

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, no unnecessary words. Front-loaded with key information: purpose, optional filter, and return fields.

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?

Low complexity tool with output schema present, so return value details not needed. However, lacks clarification of what happens with no parameters (e.g., returns default trending or recent). Minor gap.

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 has 100% coverage with parameter descriptions. Description only mentions tag filtering and limit default/max, which is already in schema. No major additional meaning beyond schema.

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 ('Get') and resource ('trending or recent DEV.to articles') with optional tag filtering. Distinguishes from siblings like 'get_article' (single article) and 'search_articles'.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., 'search_articles' or 'get_article'). Only implied that tag filtering is optional.

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