Skip to main content
Glama

Feodotracker

by io.github.pipeworx-io

What Can I Ask Pipeworx?

suggest_questions
Read-onlyIdempotent

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already provide readOnly, idempotent, and non-destructive hints. Description adds behavioral context: returns category-bucketed example questions with tool+argument shapes, drawn from live catalog. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is front-loaded with examples and well-structured. Every sentence adds value, though slightly verbose with long list of categories. Could be more concise but no wasted words.

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 no output schema, description fully explains return values (category-bucketed example questions with tool+argument shapes). Covers use case, arguments, and scope adequately.

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 coverage is 100% with one optional parameter. Description adds concrete examples of topic values ('finance', 'pharma', etc.) and explains behavior when omitted, adding meaning beyond schema.

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 it's the onboarding entry point, specifies the resource (Pipeworx capabilities), uses specific verbs (suggest, return), and distinguishes from sibling tools by directing to use it first when unsure what Pipeworx can do.

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 tells when to use ('Use this FIRST when you do not yet know what Pipeworx can do') and provides examples of queries. Mentions alternatives (meta-tools) but does not explicitly list when not to use.

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