Skip to main content
Glama

Worms

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

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

Annotations already indicate read-only and idempotent behavior; description adds scoping details and pairing with remember/forget, adding 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?

Concise single paragraph, front-loaded with main action, every sentence adds value.

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?

Despite no output schema, description covers usage, scoping, and pairing; could mention return format but adequate given simplicity.

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%; description explains that omitting key lists all saved keys, adding meaning 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 clearly states the tool retrieves a value saved via 'remember' or lists all keys, using specific verbs and distinguishing it from sibling tools like '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 'Use to look up context the agent stored earlier' and explains scoping, but does not state explicit when-not-to-use scenarios.

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

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

Multiple tool clusters blur together: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, and bet_research all route natural-language questions to sources with overlapping response shapes. The Polymarket family is better differentiated, but an agent faces real selection risk among the query family.

Naming Consistency3/5

All tools use snake_case, which is good, but verb conventions vary widely: ask_/get_/search_/list_/validate_/generate_/scan_ plus noun-only names like ai_visibility_check, entity_profile, bet_research, and the pipeworx_* prefix. The pattern is readable but not predictable enough to guess a tool's function from its name alone.

Tool Count2/5

34 tools is well past the 25+ threshold for a coherent tool set. The server tries to be a universal data gateway, prediction-market toolkit, memory store, subscription manager, WoRMS lookup, and dependency scanner all at once—scope creep that makes the surface unreasonably large.

Completeness2/5

For a data-access server there are notable holes: pipeworx:// citation URIs are advertised as fetchable but no tool resolves them directly; subscriptions can be created, listed, and cancelled but not updated or paused; and the WoRMS component (which matches the 'Worms' server name) has only three lookup tools with no synonym/distribution/export coverage.

Resources