Skip to main content
Glama

Ebi Ols

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
Behavior5/5

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

Annotations already indicate read only, idempotent, and non-destructive. The description adds meaningful behavioral context: the scoping to caller identifier, the behavior of listing all keys when omitted, and that values were previously saved via remember. No 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?

Three concise sentences cover purpose, usage, scoping, and pairing with siblings. Each sentence earns its place; the first sentence immediately states the action and optional mode, and the rest add necessary context without 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 one-optional-parameter tool with strong annotations, the description fully covers what the tool does, when to use it, who it is scoped to, and how it relates to remember/forget. No output schema is needed given the simple retrieval semantics.

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?

The schema already documents the 'key' parameter with a clear description and examples. The tool description restates the omit-to-list behavior but does not add new semantic detail beyond the schema, so baseline 3 is appropriate.

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 when omitted. It names the sibling tools (remember/forget) and provides concrete use cases (target ticker, address, research notes), distinguishing it from alternatives.

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 tells when to use: to look up previously saved context without re-deriving it. It also explains pairing with remember (save) and forget (delete), giving clear guidance on alternatives and scope (anonymous IP, BYO key hash, account ID).

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

All Ebi Ols 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

B3.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially among Pipeworx query tools (ask_pipeworx, ask_pipeworx_grounded), betting research tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread), and memory tools (remember, recall, forget). An agent could easily select the wrong tool. Additionally, tools like 'discover_tools', 'search', and 'search_within' have unclear boundaries.

Naming Consistency3/5

Most tool names use snake_case (e.g., 'entity_profile', 'validate_claim'), but there are inconsistencies with single-word verbs like 'forget', 'recall', 'remember', 'subscribe', 'unsubscribe', and the mixed pattern of 'ask_pipeworx' vs 'pipeworx_feedback'. Overall, the naming is somewhat consistent but not fully predictable.

Tool Count3/5

With 32 tools, the server has a high but not extreme count. However, the tools span multiple unrelated domains (ontologies, financial data, betting, memory, subscriptions, AI visibility), making the server feel like a collection of disparate features rather than a focused toolset. This reduces the appropriateness of the count for a single server.

Completeness2/5

The tool surface has significant gaps. For example, ontology tools lack create/update/delete operations; betting tools only provide research and analysis but no placement; memory tools allow save/recall/delete but not update; and there is no tool for user authentication or account management despite subscription features. The server covers many areas but none completely.

Resources