Skip to main content
Glama

Digitalnz

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

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

Annotations already cover safety (readOnly, idempotent, non-destructive). Description adds listing behavior and scope identifier, enhancing transparency 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, front-loaded with core functionality, no redundant information.

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?

Given simple tool (1 optional param, no output schema), description fully explains behavior, scope, and pairing with siblings, sufficient for agent 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 already describes parameter 'key' and listing behavior. Description adds concrete examples of memory contents (ticker, address, notes), providing extra context.

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 uses specific verbs ('retrieve', 'list') and resource ('value saved via remember', 'all saved keys'), clearly differentiating from siblings '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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when to use (look up context like ticker, address, research notes) and scope (scoped to identifier). Lacks explicit 'when not to use' but is clear given sibling pairs.

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

All Digitalnz 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 are difficult to distinguish: ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx_grounded, deep_research, and ask_pipeworx have fuzzy boundaries. The polymarket_* family plus bet_research also overlap heavily, requiring agents to carefully parse long descriptions to avoid misselection.

Naming Consistency4/5

Naming is predominantly snake_case with a verb-first pattern (ask_, search, subscribe, unsubscribe, list_) and clear prefix families like polymarket_ and pipeworx_. Minor deviations like ai_visibility_check and entity_profile use noun-first phrasing, but the overall pattern is still predictable and readable.

Tool Count2/5

33 tools is heavy for any single server, and the count is especially inappropriate given the server is named Digitalnz but only two tools (search, record) serve that domain. The rest form an unrelated grab-bag of data research, prediction-market, AI-visibility, memory, and utility tools.

Completeness3/5

The research workflow is fairly well covered: ask/grounded/deep modes, entity resolution, comparisons, claim validation, subscriptions, and alerts all exist. However, the DigitalNZ surface is nearly absent—just search and record—which is a significant gap for the declared server name, while other domains like AI visibility and npm dependencies are isolated one-offs.

Resources