Skip to main content
Glama

Currents

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. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. Description adds scoping detail (by identifier) and listing behavior, but doesn't contradict annotations. Adds moderate value beyond 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?

Four concise sentences, front-loaded with main action. No unnecessary words or repetition. Efficient.

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?

With no output schema, the description explains return types (value or list of keys) but doesn't detail format. Given low complexity (1 optional param), it's sufficiently complete for agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with the schema describing the key parameter. The tool description repeats that omitting key lists all keys, adding no new semantics. Baseline 3 is appropriate.

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?

Clearly states the tool retrieves saved values or lists keys, with specific verb ('retrieve') and resource ('values saved via remember'). Distinguishes from siblings '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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use: to look up previously stored context without re-deriving. Provides examples (ticker, address, notes) and mentions scoping. No explicit when-not-to-use, but pairing with siblings is implied.

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

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

Several tool clusters are hard to tell apart: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers (beta currently behaves exactly like stable), and the six polymarket_* tools plus bet_research all overlap around edge and arbitrage discovery. The descriptions are detailed and help, but an agent must read carefully to avoid misselecting a sibling tool.

Naming Consistency3/5

Names are consistently lowercase snake_case, but the verb/noun ordering is mixed: verb-first names (ask_pipeworx, list_categories, resolve_entity) coexist with noun-first names (polymarket_edges, entity_profile, pipeworx_feedback, recent_alerts) and bare verbs (remember, recall, forget). Readable overall, but the pattern is not systematic.

Tool Count2/5

34 tools is well beyond the 25+ threshold and spans at least six loosely related domains (news, structured data research, prediction markets, AI visibility, memory, subscriptions), making the server feel like a multi-product grab bag. Meta-tools like discover_tools, suggest_questions, and pipeworx_trending add further navigation overhead.

Completeness4/5

Within each bundled domain the lifecycle is well covered: data lookup has routing, grounded mode, deep research, entity resolution, comparison, and claim validation; Polymarket has research, arbitrage, edge, fill-risk, and cross-venue spread tools; memory and subscriptions each have full CRUD-ish flows. Minor gaps like subscription updating or direct article-by-ID fetching are workarounds rather than dead ends.

Resources