Skip to main content
Glama

Data Ua

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds behavioral detail about scoping (anonymous IP, BYO key hash, account ID) and listing behavior when key is omitted. 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?

Two concise sentences with key action front-loaded. Technical scoping detail added without fluff. Every sentence adds value.

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 mentions returning a value or list of keys. Scope and pairing with sibling tools are covered. Sufficient for a simple read-only retrieval tool.

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?

Schema coverage is 100% (single key parameter well described). Description reinforces that omitting key lists all keys, which is already in schema examples. Little additional meaning beyond 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 retrieves a value saved via remember or lists all keys when key is omitted, distinguishing it from sibling tools like remember and forget. Use case examples like retrieving user's target ticker or research notes further clarify purpose.

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?

Explicitly states when to use: to look up previously stored context without re-deriving. Mentions pairing with remember and forget. Scoping to identifier adds clarity, but does not explicitly mention when not to use compared to other retrieval tools.

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

All Data Ua 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.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, though the three ask_pipeworx variants (standard, beta, grounded) are very similar, potentially causing confusion. The Polymarket and memory tool families are well-differentiated.

Naming Consistency5/5

All tool names use snake_case consistently, with a clear verb_noun pattern (e.g., resolve_entity, search_datasets, subscribe). No mixing of conventions.

Tool Count4/5

34 tools is high but justified given the breadth of the Pipeworx platform and Ukraine Open Data integration. The set covers a wide range of data sources and operations without feeling bloated.

Completeness4/5

The tool surface is thorough, covering querying, comparison, profiling, subscriptions, and memory. Minor redundancy in ask_pipeworx variants, but no significant gaps for the stated data-access purpose.

Resources