Skip to main content
Glama

Cataas

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds significant context beyond annotations: scope by identifier, persistence duration (24 hours for anonymous, persistent for authenticated), and pairing with recall/forget. No contradictions with 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?

Five sentences, front-loaded with purpose. Every sentence adds value—usage, pairing, behavioral details—with no unnecessary words.

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?

Comprehensively covers purpose, usage, behavioral traits, pairing, and persistence. For a simple memory tool with two params and no output schema, no gaps remain.

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 well-described parameters. Description reinforces key-value pair concept but adds minimal extra semantic detail beyond usage context; deserves baseline score for high schema coverage.

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 saves data for later reuse, specifying a verb ('save') and resource ('data'). It differentiates from siblings by explicitly pairing with 'recall' and 'forget', establishing its unique role in memory management.

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?

Provides explicit guidance on when to use: 'when you discover something worth carrying forward... so you don't have to look it up again.' Mentions pairing with recall and forget but does not include 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 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.7/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route natural-language questions to the same underlying data catalog, and the polymarket_* family has several near-synonymous scanning tools. Entity_profile, compare_entities, and recent_changes also have fuzzy boundaries. Only the three cat tools are clearly distinct, but an agent could easily pick the wrong tool across the Pipeworx family.

Naming Consistency3/5

The names are consistently snake_case and several families share clear prefixes like ask_pipeworx, polymarket_, and list_. However, the set mixes imperative verb-first names with noun-style names, and the cat_* tools do not share any naming pattern with the dominant Pipeworx family.

Tool Count2/5

34 tools is too many for a server named Cataas, and only 3 of them are actually cat-related. The other 31 tools belong to an unrelated data-research and prediction-market platform, making the tool count inappropriate for the apparent purpose.

Completeness2/5

As a cat-image server, the surface is thin: random_cat, cat_by_tag, and list_tags cover basics but omit common Cataas operations like GIFs or text-on-cat. As a data-research platform, the cat tools are noise, so the mixed set is incomplete and incoherent for either apparent purpose.

Resources