Skip to main content
Glama

Feodotracker

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

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

Description adds scoping details (identifier-based isolation) beyond annotations which already indicate read-only, idempotent, non-destructive behavior. 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?

Three sentences with front-loaded action and no superfluous words. Each sentence serves a purpose: core action, usage context, and pairing with other tools.

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?

Covers purpose, usage, and behavioral context well. Lacks explicit mention of return format (value or list of keys), but for a simple read tool with good annotations, this is a minor gap.

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% and description does not add new parameter details beyond what is in the schema (e.g., 'omit to list all keys' is already there). Baseline 3 is appropriate.

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?

Description clearly states the tool retrieves a value or lists keys, with specific verb ('Retrieve', 'list') and resource ('value previously saved'). It distinguishes from siblings 'remember' and 'forget' by mentioning pairing. Examples in schema reinforce 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 says 'Use to look up context... without re-deriving' and mentions pairing with remember and forget. However, it doesn't explicitly state when not to use or name alternatives beyond those implied by the sibling context.

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

All Feodotracker 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

Multiple tools occupy the same conceptual space: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all answer 'what can this server do' or 'look this up' in overlapping ways. The Polymarket suite (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) and the memory trio (remember, recall, forget) also create boundary confusion despite long descriptions.

Naming Consistency2/5

Naming is a mixed bag: some tools are imperative verbs (check_ip, forget, remember, validate_claim), some are bare nouns or adjectives (list, recent, aggressive), and many are noun compounds (entity_profile, polymarket_edges, pipeworx_trending). No consistent verb_noun or domain-prefix pattern holds across the set.

Tool Count2/5

35 tools is excessive for a server ostensibly named Feodotracker, whose core blocklist surface is only four tools (list, recent, aggressive, check_ip). The rest is a sprawling collection of unrelated Pipeworx, Polymarket, memory, subscription, and utility features that would be better split into separate servers.

Completeness3/5

The core blocklist domain is minimally covered: you can list, filter by family/status, check an IP, and see recent additions, which covers basic read-only use. However, there are notable gaps and dead ends, such as no historical lookup beyond recent hours and no per-IP detail beyond membership, while the bundled Pipeworx/Polymarket features are thorough but make the overall surface feel scattershot.

Resources