Skip to main content
Glama

Crypto Fng

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

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

Adds value beyond annotations (readOnlyHint, etc.) by explaining scoping to identifier and pairing with other tools. No contradictions 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 tightly written sentences with no wasted words. Front-loaded with core action. Every sentence adds value.

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 tool with one optional parameter and no output schema, the description fully explains behavior, scoping, and relationship to siblings. Complete and self-contained.

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% with description for the single parameter. Description adds a brief context but no additional semantics beyond the schema's 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 two actions: retrieve a value saved via remember, or list all keys when key is omitted. Uses specific verbs (retrieve, list) and distinguishes from sibling tools (remember, 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?

Describes use case (look up stored context) and pairing with remember/forget, but does not explicitly state when not to use or mention specific alternatives beyond sibling list.

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

All Crypto Fng 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 overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route questions through the same underlying catalog with only subtle differences. The polymarket family (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) also has fuzzy boundaries. Only the Crypto Fear & Greed tools are clearly distinct.

Naming Consistency3/5

Most tools follow a snake_case verb_noun pattern, but there are notable deviations: the ask_pipeworx_* family uses object-style names, pipeworx_feedback and polymarket_edges are noun_noun, and current_index vs index_history uses 'index' inconsistently. The polymarket_* family mixes verb and noun styles internally.

Tool Count2/5

33 tools is heavy for a server ostensibly named 'Crypto Fng' — only 2 of the tools relate to that core purpose. The rest constitute a broad generic data-research and prediction-market platform that would be more appropriately scoped as its own server. The count exceeds the comfortable range for an agent to reason over.

Completeness4/5

Within the actual (broad) domain, the surface is fairly complete: discovery (discover_tools, suggest_questions), querying (ask_pipeworx family), grounded verification (validate_claim, ask_pipeworx_grounded), deep research, entity resolution/profile/comparison, memory lifecycle, and subscription lifecycle. The named crypto-sentiment domain is fully covered with current and historical index tools, though the underlying 5,708 pack tools are only reachable indirectly through the router.

Resources