Skip to main content
Glama

Ted Eu

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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent nature. Description adds scoping to identifier and pairings with remember/forget, providing useful context 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?

Three concise sentences, each adding value. Front-loaded with primary action, no redundancy.

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 retrieval tool: explains behavior, scope, and relationship to sibling tools. No output schema needed given simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single optional parameter 'key' is well-described in both schema and description. Description clarifies omission behavior for listing all keys.

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?

Clearly states verb 'Retrieve' and resource 'value previously saved via remember' or list all keys. Distinguishes from siblings like 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 says when to use (look up stored context) and when not (omit key for listing). Mentions pairing with remember and forget.

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

All Ted Eu 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.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose described in detail. Even tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are differentiated by hallucination resistance, account requirements, and use cases. Polymarket tools are each specialized (arbitrage, edges, fill risk, etc.). No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow snake_case consistently. They use descriptive verb-noun patterns (e.g., ask_pipeworx, bet_research, compare_entities, subscribe). No mixing of conventions or ambiguous names.

Tool Count4/5

32 tools is on the higher side but justified by the server's broad scope covering company research, prediction markets, data lookups, memory, subscriptions, and more. Each tool serves a distinct function, though the count might feel slightly heavy for a single server.

Completeness4/5

The toolset covers core workflows for company analysis, prediction market operations, data retrieval, and system management (memory, subscriptions). Minor gaps exist (e.g., no direct tool for non-company entity profiles beyond drugs), but the overall surface is comprehensive for the intended multi-purpose assistant.

Resources