SiteCheck Web Intel

DEV Community latest articles for one tag: title, author

search_dev_to_articles

Read-only

DEV Community (dev.to) latest articles for one tag (public DEV API, no key): title, author, publish time, reactions, comments, reading time and link. Search by tag only; the public API has no free-text search. Related tools on this server, for a different need: search_al_jazeera_articles when you need Al Jazeera latest articles from its public RSS feed; search_ap_news_articles when you need Latest Associated Press articles: headline, publisher. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "tag": "<tag>"
    },
    "name": "search_dev_to_articles"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	Yes	One tag name, letters and digits only, e.g. javascript
`limit`	No	How many articles, 1 to 30 (default 10)

Output Schema

Name	Required	Description	Default
`tag`	No
`count`	No
`items`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious operational context: no API key required, x402 payment of $0.002 USDC per successful call, and that failed calls are not charged — details an agent must know before invoking. It does not describe limits or rate behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and field list are front-loaded in the first sentence, with constraints and alternatives following. It loses a point for padding the sibling mentions with redundant per-sibling field lists ('headline, publisher') that add little routing value.

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

Completeness5/5

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

With an output schema present and full parameter documentation, the description needn't explain return values. It still covers the two things structured fields cannot: payment mechanics and the tag-only search limitation.

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 coverage is 100% and both parameters carry their own constraint text (letters and digits only, range 1–30, default 10). The description adds only the reinforcement that the tag is a single tag and no free-text query is supported, which is marginal over the schema baseline.

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?

Names a specific verb and resource ('DEV Community latest articles for one tag'), enumerates the returned fields, and explicitly differentiates itself from two named siblings. An agent can tell instantly this is tag-scoped dev.to article retrieval, not general news search.

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

Usage Guidelines5/5

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

States the operative constraint plainly ('Search by tag only; the public API has no free-text search') and routes the agent to specific alternatives (search_al_jazeera_articles, search_ap_news_articles) keyed to when each applies. Both the when-to-use and when-not-to-use cases are covered.

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

All SiteCheck Web Intel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?