Skip to main content
Glama

Data Ny

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

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

The description adds behavioral context beyond annotations by stating 'Scoped to your identifier (anonymous IP, BYO key hash, or account ID)' and the behavior of listing all keys when omitted. Annotations already disclose read-only, idempotent, and non-destructive nature, so this is additional useful context.

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 sentences, front-loaded with the primary purpose, and every sentence provides meaningful detail without redundancy or 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-parameter read-only tool with no output schema, the description fully covers purpose, usage context, scoping, and relationships to sibling tools, making it adequate for an agent to select and invoke the tool correctly.

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?

The schema already covers the key parameter with 100% description, but the tool description adds meaning by explaining that keys come from prior remember calls and that omitting the key lists all saved keys, which goes beyond the schema's simple type description.

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 function with a specific verb and resource: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' It distinguishes itself from sibling tools like remember (save) and forget (delete) by describing the retrieval action.

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?

It explicitly says when to use the tool: 'Use to look up context the agent stored earlier' and explains the benefit ('without re-deriving it from scratch'). It also mentions pairings with remember and forget, but does not name an explicit alternative tool for the same retrieval task.

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

All Data Ny 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.6/5.0
Disambiguation4/5

Most tools have distinct purposes, but ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim have overlapping functionality in answering factual questions. The detailed descriptions help differentiate them, though some confusion may still arise.

Naming Consistency5/5

All tool names follow a consistent snake_case convention with a verb_noun pattern (e.g., compare_entities, resolve_entity). No mixing of camelCase or other styles, making the naming predictable and uniform.

Tool Count3/5

34 tools is on the higher side, but many are meta-tools (discover, feedback, subscriptions) and some are redundant (ask_pipeworx vs grounded). While the scope is broad, the count could be trimmed for tighter focus.

Completeness4/5

The server covers a wide range of domains (SEC, FDA, FRED, prediction markets, etc.) with strong read and analysis capabilities. Missing update/delete operations and direct trading, but comprehensive for data retrieval and analysis.

Resources