Skip to main content
Glama

Color Pizza

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

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint false. Description adds scope (by identifier) and pairing with siblings, going beyond annotations without contradiction.

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?

The description is front-loaded with the core action, then explains use cases and pairing. Every sentence adds value without redundancy.

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?

Given no output schema, the description could specify return format (value or list of keys). It covers purpose, usage, scope, and pairing, but lacks explicit return type details.

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% with a description for the key parameter. The tool description adds context such as omitting key to list all and examples of key values, adding meaningful usage semantics.

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 by key or lists all keys when omitted. It distinguishes from siblings (remember, forget) and gives concrete examples like ticker, address, research notes.

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?

It explicitly says when to use (retrieve stored context) and how (omit key to list all). It contrasts with remember and forget but lacks explicit when-not-to-use guidance.

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

All Color Pizza 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

A4.3/5.0
Disambiguation4/5

Most tools have distinct purposes, such as `entity_profile` for company profiles and `recent_changes` for updates. However, some overlap exists between `ask_pipeworx` and `ask_pipeworx_grounded` (both query data, one with hallucination resistance), and among Polymarket-related tools (`bet_research`, `polymarket_edges`, `polymarket_arbitrage`). Detailed descriptions help distinguish them.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern (e.g., `ai_visibility_check`, `ask_pipeworx`, `bet_research`, `compare_entities`). No mixing of camelCase or other conventions. The names are descriptive and predictable.

Tool Count3/5

At 29 tools, the server is on the heavy side. While each tool serves a specific function, the broad scope (color naming, Polymarket betting, company research, etc.) makes the count feel slightly high for a single server, though still manageable.

Completeness4/5

The tool set covers color naming, company research, Polymarket, AI visibility, memory, subscriptions, and data queries comprehensively. Minor gaps exist (e.g., no direct SEC filing retrieval without compound tools), but overall it provides a well-rounded surface for its diverse domain.

Resources