Skip to main content
Glama

deckofcards

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. Added

TDQS

A4.7/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 useful behavioral context beyond annotations, particularly scoping: 'Scoped to your identifier (anonymous IP, BYO key hash, or account ID).' It also mentions the list-all behavior when the key is omitted.

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?

The description is three sentences, front-loaded with the action, and every sentence adds meaningful information. No fluff or redundancy.

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 tool with one optional parameter, strong annotations, and no output schema, the description is fully adequate. It explains the purpose, usage, scoping, and relationship to sibling tools.

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% and the schema already documents the parameter ('Memory key to retrieve (omit to list all keys)'). The description reinforces the omission behavior and adds examples of what keys might contain, providing modest semantic enrichment beyond the 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 uses a specific verb ('Retrieve') and clearly states the resource ('a value previously saved via remember') and the alternative behavior ('list all saved keys'). It distinguishes itself from siblings by explicitly referencing 'remember' and 'forget'.

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?

It provides explicit usage context: 'Use to look up context the agent stored earlier' with concrete examples (target ticker, address, research notes). It also pairs with siblings ('Pair with remember to save, forget to delete'), giving direct guidance on when to use this tool versus alternatives.

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

All deckofcards 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

Multiple tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are functionally identical (beta just has experimental routing), and the Polymarket suite (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) all revolve around prediction-market signal detection with unclear boundaries. Also ai_visibility_check and scan_competitor_ai_presence overlap heavily.

Naming Consistency2/5

Naming is a mix of verb-first (draw_cards, resolve_entity, discover_tools) and noun-first (entity_profile, new_deck, recent_alerts) styles, with inconsistent prefixes (pipeworx_feedback vs ask_pipeworx) and no unifying convention. Some tools are bare verbs (recall, remember), others are noun phrases (polymarket_edges).

Tool Count2/5

34 tools is excessive for a server named 'deckofcards' — only 3 tools relate to cards. Even as a general-purpose data/research server, 34 is on the high end and includes many near-duplicates (ask_pipeworx variants) and highly specialized tools that could be consolidated.

Completeness3/5

The research side is fairly complete (lookup, grounding, comparison, profiles, claim verification, memory, subscriptions), but the card-deck functionality is minimal (only create, draw, shuffle) and lacks any deck inspection or hand management. The server's scope is unclear, making it hard to assess true coverage.

Resources