Skip to main content
Glama

Cataas

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

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

Annotations already indicate read-only and idempotent nature. Description adds scoping detail (per identifier) and listing behavior, going 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?

Two sentences convey core action, usage, and pairing with minimal words. Well front-loaded and no fluff.

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 parameter and good annotations, the description covers purpose, scope, pairings, and usage examples completely.

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%, but description adds meaningful context: the parameter's dual role (specific key retrieval vs list all on omit) and practical examples.

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?

Specifically states it retrieves a value saved via remember or lists all keys, distinguishing it from 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?

Explicitly explains when to use (look up stored context) and mentions alternatives (save with remember, delete with forget), providing clear usage guidance.

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

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

Several tools intentionally overlap: ask_pipeworx_beta is explicitly identical to ask_pipeworx, and ask_pipeworx/ask_pipeworx_grounded/deep_research plus discover_tools/suggest_questions sit close together. The long descriptions clarify differences, but an agent still has to choose between near-equivalent entry points.

Naming Consistency3/5

All names are readable snake_case, but there is no single consistent convention: verb-led names like list_tags and resolve_entity sit alongside noun-led names like random_cat, entity_profile, and polymarket_arbitrage. Domain prefixes like polymarket_ and pipeworx_ help, but the mixed grammar makes the surface less predictable.

Tool Count2/5

34 tools is far beyond what a cat-image server needs; only 3 tools relate to Cataas, while the rest form a sprawling Pipeworx data, prediction-market, memory, and subscription suite. The count is in the 'too many' range and most tools are outside the server's apparent stated domain.

Completeness3/5

The cat-image core covers random cats, tag-filtered cats, and tag listing, but omits other Cataas-style operations like fetching by cat ID or creating cat images with text/effects. The embedded Pipeworx side is broad, but it does not fill the gaps in the server's named cat API purpose.

Resources