Skip to main content
Glama

Edmtrain

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

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds scoping detail (anonymous IP, BYO key hash, account ID) and listing behavior on omit. 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 with zero wasted words. Core action front-loaded, then context and pairing. Ideal length.

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?

No output schema, but description covers retrieval and listing. Missing return format (e.g., value type or list structure), but pairing with remember reduces ambiguity. Sufficient for a simple tool with good sibling context.

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 100% and description adds meaning: explains that omitting key lists all saved keys. This enriches the schema's 'omit to list all keys' hint.

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?

Description clearly states verb+resource: 'Retrieve a value previously saved via remember, or list all saved keys'. It distinguishes from siblings by naming remember and forget as complementary tools.

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 states when to use ('look up context the agent stored earlier') and how it is scoped. Names alternatives (remember to save, forget to delete), providing clear guidance.

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

All Edmtrain 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.9/5.0
Disambiguation2/5

Several tools have overlapping or near-identical purposes: ask_pipeworx and ask_pipeworx_beta are currently functionally identical, ask_pipeworx_grounded is the same router with an extraction step, and discover_tools vs suggest_questions both serve as 'what can I do here' entry points. The polymarket_* family is more distinct, but the ask_pipeworx/deep_research overlap alone makes tool selection genuinely ambiguous.

Naming Consistency4/5

The vast majority of tools follow lowercase snake_case with recognizable domain prefixes (ask_pipeworx*, polymarket_*, pipeworx_*), which is a decent pattern. However, there are bare-noun tools (events, locations, recall, forget) and mixed verb-first vs noun-first ordering (list_subscriptions vs entity_profile, scan_dependency vs polymarket_edges), so it is not perfectly uniform.

Tool Count2/5

33 tools is well above the comfortable range and feels heavy even for a broad data-research platform. Many tools are narrow variations (five polymarket analysis tools, four ask_pipeworx variants, three memory tools) that could plausibly be consolidated or exposed as parameterized modes rather than separate top-level tools.

Completeness4/5

For the actual domain suggested by the tool names and descriptions—structured data research, entity profiling, claim verification, and prediction-market analysis—the surface is quite complete: lookup, grounded answers, deep research, comparisons, recent-change tracking, subscriptions, memory, and arbitrage/fill-risk analysis are all covered. However, relative to the server name 'Edmtrain', the event-discovery surface is extremely thin (only events and locations), which is a notable mismatch.

Resources