devto-mcp-server

search_by_tech

Find articles by technology or tag. Optionally retrieve top posts from recent days using top_days parameter.

Instructions

Search articles by technology/tag. Convenience wrapper around search.

Args: tech: Technology or tag (e.g. 'python', 'fastapi', 'mcp', 'ai'). per_page: Number of results. top_days: Return top articles from last N days (7, 30, etc.). If None, does text search on tag.

Returns: List of matching articles.

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": {
      "tech": "<tech>"
    },
    "name": "search_by_tech"
  }
}

Input Schema

Name	Required	Description	Default
`tech`	Yes
`per_page`	No
`top_days`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided; description only mentions it returns a list of articles but omits whether the tool is read-only, requires authentication, or any side effects.

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?

Description is concise (5 lines), well-structured with clear argument descriptions, and no superfluous text.

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

Completeness3/5

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

Explains purpose, parameters, and return value, but lacks explicit differentiation from siblings and does not cover error cases or edge effects. Output schema exists but is not detailed.

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

Parameters5/5

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

With 0% schema description coverage, the description adds significant meaning: explains tech with examples, per_page as result count, and top_days with conditional behavior (None triggers text search).

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 clearly states the tool searches articles by technology/tag and identifies itself as a convenience wrapper, distinguishing it from sibling tools like search_devto_posts.

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?

Provides parameter-level guidance (e.g., top_days behavior) but does not explicitly state when to use this tool over sibling search_devto_posts or when not to use it.

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

Deploy Server