Skip to main content
Glama

Stratz

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 indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, which are consistent with 'retrieve' and 'list'. The description adds value by explaining that omitting the key lists all saved keys, that the tool is scoped to an identifier, and it mentions pairing with remember/forget. 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?

The description is concise with four sentences. The first sentence states the core purpose. Subsequent sentences provide usage context, scoping, and pairing. Every sentence adds value without 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 and no output schema, the description covers all necessary aspects: purpose, usage, scoping, and relationship with sibling tools. No gaps are apparent.

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% (only one parameter 'key' with description). The description adds meaning by explaining that omitting the key lists all keys, which goes beyond the schema. The examples in the input schema further clarify usage.

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 specifies the verb 'Retrieve' and 'list', the resource 'value saved via remember', and distinguishes from siblings like 'remember' and 'forget'. It gives specific examples of what to retrieve (ticker, address, notes), making the purpose unambiguous.

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 explicitly states when to use the tool: 'to look up context the agent stored earlier' and provides concrete examples. It mentions scoping to the agent's identifier. However, it does not explicitly mention when not to use it or alternatives beyond pairing with remember/forget.

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

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

Several tools have overlapping or intentionally duplicated purposes: ask_pipeworx/ask_pipeworx_beta currently behave identically, and the Polymarket cluster (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, polymarket_kalshi_spread) presents multiple scanners with fuzzy boundaries. The long descriptions help, but the set as a whole is hard to navigate without close reading.

Naming Consistency2/5

Naming is a mix of bare single nouns (hero, match, meta, remember, forget), snake_case verb-first names (ask_pipeworx, compare_entities, generate_llms_txt), and noun-first compounds (pipeworx_feedback, bet_research, scan_competitor_ai_presence). There is no consistent verb_noun or noun-verb convention across the set.

Tool Count2/5

At 43 tools, the server bundles at least five unrelated domains (Dota 2 stats, Pipeworx data querying, Polymarket analytics, memory, subscriptions, AI visibility). That is far too many for a focused MCP server, and the mix makes the surface feel like a grab bag rather than a purpose-built toolkit.

Completeness4/5

Each subdomain individually has solid coverage: Dota 2 has heroes/matches/players/tournaments/meta plus a GraphQL fallback, the data layer has discovery + routing + grounding + validation, and memory/subscriptions have full lifecycle operations. The only real gap is cohesion across domains; within each slice there are no obvious dead ends.

Resources