Skip to main content
Glama

Tech Feeds

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

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

Adds context beyond annotations: omitting key lists all keys, scoped by identifier, and 'without re-deriving it from scratch' implying a persistence mechanism. No contradiction with annotations (readOnlyHint, idempotentHint, destructiveHint all consistent).

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?

Four sentences covering function, usage rationale, scoping, and sibling relationships. No wasted words; front-loaded with the core action.

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?

Complete for a simple tool with one optional parameter and no output schema. Covers all necessary context: listing behavior, scoping, and relationship to remember/forget.

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%, so baseline is 3. The description reinforces the schema's description of the 'key' parameter and adds context about listing all keys when omitted, but doesn't add new semantic details beyond what the schema provides.

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's purpose: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' It provides concrete use cases and distinguishes from sibling tools '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 this tool ('to look up context the agent stored earlier') and specifies when to use alternatives ('Pair with remember to save, forget to delete'). Also clarifies scoping ('Scoped to your identifier').

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

All Tech Feeds 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

Many tools have overlapping purposes, e.g., multiple ask_pipeworx variants, bet_research vs. polymarket_edges, and several entity/profile tools. An agent could easily misselect between similar tools despite detailed descriptions.

Naming Consistency2/5

Tool names are inconsistent: some use snake_case (ask_pipeworx), some camelCase (ai_visibility_check), and verbs vary (ask, bet, compare, scan, validate). No clear naming convention is followed across the set.

Tool Count3/5

With 34 tools, the server covers a broad range of functionalities for a platform like Pipeworx. While each tool seems justified, the count is on the higher end, potentially overwhelming for simpler use cases.

Completeness4/5

The tool set covers data retrieval, memory, subscriptions, Polymarket analysis, and utility functions comprehensively. Minor gaps exist (e.g., no direct user management) but core workflows are well-supported.

Resources