Skip to main content
Glama

Codewars

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by explaining the behavior of omitting the key to list all keys and the scope (IP, key hash, account ID). No contradictions.

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 concise sentences with key information front-loaded. Every sentence adds value: first states core action, second gives examples and context. No waste.

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?

For a simple retrieval tool with one optional parameter and no output schema, the description covers purpose, usage, scoping, and pairing with related tools. It leaves no obvious gaps.

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 of the 'key' parameter. The description reinforces that omitting the key lists all keys, which adds practical context beyond the schema. Could mention return format but not necessary given simplicity.

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 retrieves a value by key or lists all keys, distinguishing it from siblings like 'remember' and 'forget'. It specifies the resource (values saved via remember) and the action (retrieve/list).

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?

The description explains when to use: to look up stored context without re-deriving. It mentions scoping and pairing with 'remember' and 'forget'. However, it does not explicitly state when not to use or provide alternatives beyond the explicit pairings.

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

All Codewars 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.5/5.0
Disambiguation2/5

The 4 Codewars tools (kata, user, user_authored, user_completed) are distinct, but the 31 Pipeworx tools create real overlap: ask_pipeworx, ask_pipeworx_beta (explicitly 'currently matches ask_pipeworx exactly'), and ask_pipeworx_grounded are near-twins of the same router, and the five polymarket_* tools (edges, arbitrage, edge_tracker, fill_risk, kalshi_spread) have heavily overlapping opportunity-discovery purposes. discover_tools and suggest_questions also both serve as 'what can I ask' entry points. Agents will misselect between the three ask_pipeworx variants and across the prediction-market suite.

Naming Consistency2/5

Naming conventions are mixed: bare nouns (kata, user), bare verbs (forget, remember, subscribe), adjective_noun (recent_alerts, recent_changes), verb_noun (validate_claim, bet_research), and noun_verb (user_authored, user_completed) all appear. Even within the small Codewars family the prefix style is inconsistent — kata and user are bare nouns while user_authored and user_completed expect a user_ prefix, and remember/recall/forget use a different verb style than the rest of the server.

Tool Count2/5

35 tools exceeds the 25+ 'too many' threshold for a coherent server. Worse, 31 of the 35 are Pipeworx meta-research tools unrelated to the server's namesake (Codewars), so the count is drastically inflated relative to its apparent purpose — the server presents a full finance/prediction-market/research gateway while contributing only 4 tools to its advertised domain.

Completeness2/5

The actual Codewars surface has significant gaps: kata, user, user_authored, and user_completed are purely read-only, with no solution submission, attempt/training history, leaderboard access, or kata search by difficulty/language. Meanwhile the Pipeworx side is over-complete for a server not named for it, leaving the server's stated identity under-covered with no way to perform any write operation on the Codewars platform.

Resources