Skip to main content
Glama

Datalastic

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

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

Annotations already declare read-only, non-destructive, and idempotent behavior. The description adds valuable context beyond that: scoping to an identifier (anonymous IP, BYO key hash, account ID), the omit-key behavior for listing all keys, and the lifecycle pairing with remember/forget. No contradiction with 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?

The description is three focused sentences: the first states action and alternative, the second gives usage examples, the third covers scoping and sibling relationships. Every sentence earns its place with no fluff.

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 the tool's simplicity (one optional parameter, no output schema), the description covers purpose, usage, scope, and relationships. It doesn't specify behavior for missing keys, but the examples and clear statement of retrieve/list behavior make it nearly complete for typical use.

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% and the key parameter description is clear. The tool description supplements the schema by explaining that keys are 'previously saved via remember', adding context about the key's origin that is not present in the schema.

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 primary action ('Retrieve a value') and resource ('previously saved via remember'), plus the alternative behavior ('list all saved keys'). It distinguishes from siblings by explicitly referencing 'remember' and 'forget' as paired tools.

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?

The description says 'Use to look up context the agent stored earlier' and provides concrete examples (target ticker, address, research notes), giving clear when-to-use guidance. It names alternatives ('remember' to save, 'forget' to delete) but doesn't explicitly state when not to use the tool.

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

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

Several tools occupy nearly the same question-answering role: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all accept natural-language factual queries, and ask_pipeworx_beta is explicitly identical to ask_pipeworx today. The polymarket_* family also has overlapping opportunity-detection responsibilities, so an agent can easily select a near-duplicate tool for the same intent.

Naming Consistency4/5

Tool names are uniformly lowercase snake_case and use recognizable domain prefixes like ask_pipeworx_, polymarket_, datalastic_, and pipeworx_, which makes the set easy to group. The main deviation is that some names are verb-first (ask, compare, subscribe) while others are noun phrases (entity_profile, recent_alerts, bet_research), but this is minor and readable.

Tool Count2/5

At 33 tools this exceeds the 25+ threshold for a single server, and many of them are meta-tools or overlapping research/opportunity scanners that could be consolidated. The breadth is justified only partially; several utilities like generate_llms_txt and scan_dependency feel bolted on.

Completeness3/5

As a general research and monitoring toolkit it covers the full life cycle: discover, ask, verify, compare, profile, cite, remember, subscribe, and alert. But the server is named Datalastic yet the maritime surface is thin (only live position and radius lookup, no historical tracking, port calls, or fleet tools), and a few one-off utilities don't fit a coherent domain.

Resources