Skip to main content
Glama

disify

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.7/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, so the safety profile is covered. The description adds valuable context beyond annotations: it discloses the dual behavior (retrieve single vs. list all), the scoping to identifier (anonymous IP, BYO key hash, or account ID), and the relationship with remember/forget. This enriches the agent's understanding, though return format on missing keys is not detailed.

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 front-loaded with the verb 'Retrieve' and delivers all essential information in three dense sentences. No filler or redundant phrasing; every clause earns its place, including the scoping note and companion tool pairing.

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 strong annotations, the description is fully complete. It explains functionality, usage context, scoping, and related tools. Even without an output schema, the description's phrase 'Retrieve a value' and 'list all saved keys' sufficiently conveys the expected return behavior.

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 input schema already covers the 'key' parameter at 100% with 'Memory key to retrieve (omit to list all keys).' The description adds further meaning by giving concrete examples of what keys might contain (user's target ticker, address, prior research notes) and by explaining that omitting the key yields a list, reinforcing the parameter's optionality and its role in the tool's dual behavior.

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 opens with a specific action: 'Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).' This clearly differentiates recall from its siblings remember and forget, and the examples (ticker, address, research notes) further clarify the intended resource.

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?

The description explicitly states when to use recall: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also provides exclusions and alternatives by pairing with 'remember to save, forget to delete,' giving the agent direct guidance on when not to use recall.

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

All disify 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
Disambiguation2/5

Several tools have nearly identical or heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, and the six Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) all involve finding/analyzing prediction-market opportunities. deep_research and ask_pipeworx also overlap as general query routers, and ai_visibility_check vs scan_competitor_ai_presence is another confusable pair.

Naming Consistency3/5

All names use snake_case and are descriptive, but verb placement is inconsistent: some are verb-first (check_domain, compare_entities, resolve_entity), others are verb-last or noun-like (ai_visibility_check, entity_profile, pipeworx_trending, bet_research). There is no chaotic camelCase mix, but the pattern is not predictable enough to guess a tool's behavior from its name.

Tool Count2/5

33 tools is far above the typical well-scoped range and the set spans multiple unrelated domains (data lookup, prediction markets, AI visibility, memory, subscriptions, email/domain validation) that have no cohesive purpose under the 'disify' name. Most tools are not related to domain or email checking, making the count feel like a grab bag rather than a focused toolkit.

Completeness2/5

For a server named 'disify', the core domain-validation surface is minimal (only check_domain and validate_email) and misses obvious operations like WHOIS lookup or breach/debounce checks. As a general data toolset it is broad but shallow in each area, with gaps such as entity_profile only supporting US public companies and no update/delete operations for most data resources.

Resources