Skip to main content
Glama

Wayback

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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds scoping detail (by identifier) and 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?

Three sentences: core function, usage motivation, scoping/pairing. No extraneous words. Information is front-loaded.

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?

Given the single optional parameter, no output schema, and annotations covering safety, the description fully covers behavior, scoping, and relationships with 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 description coverage is 100%. Description explains the key parameter's effect when omitted ('list all keys'), which adds behavioral context beyond the schema's property description.

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 specific verbs ('retrieve', 'list') and resources ('value saved via remember', 'saved keys'). It clearly distinguishes from sibling tools 'remember' and 'forget' by naming them.

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 states when to use (look up stored context) and when to omit the key (list all). Implicitly suggests when not to use by directing to sibling tools for save/delete. No explicit when-not conditions, but context is clear.

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

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

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical in purpose, and the five polymarket_* tools all target prediction-market analysis. The presence of a broad Pipeworx data layer alongside Wayback-specific tools under one server name further blurs boundaries.

Naming Consistency3/5

Most tools use snake_case, but the pattern varies: many follow verb_noun (get_snapshot, list_snapshots, resolve_entity, validate_claim), while others are noun_noun (entity_profile, polymarket_edges, pipeworx_feedback, bet_research). Suffixes like _beta and _grounded are used inconsistently, and some names are long and descriptive while others are terse.

Tool Count2/5

34 tools is far more than what a Wayback Machine server should need, and most tools (Pipeworx data queries, prediction-market analysis, memory, subscriptions) have nothing to do with the Wayback Machine. The server's stated purpose appears narrow, but the tool set is bloated with unrelated functionality.

Completeness2/5

For the Wayback Machine domain, only three tools are relevant (get_capture_count, get_snapshot, list_snapshots), and obvious operations like saving/archiving a URL, comparing snapshots, or handling deleted captures are missing. The Pipeworx-related tools are broad but not clearly aligned with the Wayback theme, so the core purpose is under-served.

Resources