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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

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

B3.4/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, while ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, and discover_tools all occupy adjacent lookup/discovery territory. The four Codewars tools are clear, but the broader set is genuinely hard to navigate.

Naming Consistency3/5

Most names follow a readable snake_case verb_noun style with useful prefixes like polymarket_ and user_, but there are one-word outliers (kata, user, forget, recall, remember) and inconsistent phrasing such as ai_visibility_check versus scan_competitor_ai_presence. The naming is mostly predictable but not uniform.

Tool Count1/5

35 tools is already heavy, and the server is named Codewars while only 4 of the 35 tools relate to Codewars. The remaining 31 tools belong to a completely different Pipeworx research/prediction-market/brand-visibility product, making the count both excessive and fundamentally mismatched to the server's stated identity.

Completeness1/5

For a Codewars server, the surface is severely incomplete: you can fetch a single kata and a user's profile, authored list, and completed list, but there is no search, no kata listing by rank/tag, no solution submission or training workflow, and no way to manage authored kata. The unrelated Pipeworx tools do not fill these gaps; they point at a different domain entirely.

Resources