Skip to main content
Glama

Devto

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.8/5.0
Behavior5/5

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

Adds behavioral context beyond annotations: authenticated users get persistent memory, anonymous sessions retain for 24 hours. No contradiction with 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?

Concise yet informative: each sentence adds value, front-loaded with main purpose, no fluff.

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?

Covers persistence, scoping, and pairing. No output schema but store operation doesn't require return value details. Could mention overwrite behavior but adequate overall.

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 covers 100% of parameters with descriptions. Description adds examples for key values and states value is any text, enhancing understanding beyond raw 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?

The description clearly states the tool saves data for reuse, specifies the key-value pair storage, and distinguishes from siblings recall and forget by mentioning pairing with them.

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?

Explicitly says when to use: when discovering something worth carrying forward, with examples (resolved ticker, target address, user preference). Also mentions pairing with recall and forget.

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