Skip to main content
Glama

Ens

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are all false/neutral, so the description carries the burden. It richly discloses behavior: anonymous filing returns a claim_token for later status checks, rate limit of 5 per identifier per day, free (no quota), and daily human review. This goes well beyond the minimal annotations and contains no contradiction.

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?

The description is long but every sentence adds value: purpose, use cases, exclusions, claim_token flow, rate limit, and roadmap impact. It is front-loaded with the primary purpose, but could be tightened slightly without losing 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 the tool's complexity (nested context object, zero required params, no output schema), the description covers all essentials: purpose, when-to-use, exclusions, return behavior (claim_token), rate limit, and next steps. It is complete enough for an agent to invoke correctly without additional context.

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 covers 100% of parameters with descriptions. The description adds practical semantics: instructs users to describe issues in terms of Pipeworx tools/packs (not paste end-user prompts) and explains the claim_token resurrection pattern. This enhances the schema without redundant repetition, though it does not add deep syntax details.

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 states a specific verb ('Tell') and resource ('the Pipeworx team'), and clearly defines the scope: reporting broken/missing/needed functionality. It distinguishes from siblings by explicitly limiting feedback to tools served by this Pipeworx connection and contrasting with filing for other MCP servers.

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?

Provides explicit when-to-use criteria (bug, feature/data_gap, praise) and when-not-to-use (tools from other MCP servers, with advice to file there instead). Also gives a fallback ('Not sure? Pipeworx tool names are the ones this connection lists') to resolve ambiguity.

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

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

A4.3/5.0
Disambiguation5/5

Each tool has a clearly defined, distinct purpose. Even closely related tools like ask_pipeworx and ask_pipeworx_grounded are differentiated by use case (casual vs. high-stakes), and the prediction market tools each cover a specific function (research, edge detection, arbitrage, fill risk, tracking, cross-venue spreads). Detailed descriptions eliminate ambiguity.

Naming Consistency4/5

Tool names predominantly follow a verb_noun pattern (e.g., ask_pipeworx, compare_entities, resolve_entity), but a few use noun_noun or adjective_noun forms (e.g., entity_profile, recent_alerts). The naming is generally predictable and readable, with minor deviations from a strict pattern.

Tool Count3/5

The server offers 32 tools, which is above the typical 3-15 range for a well-scoped server. However, the vast domain (financials, prediction markets, news, memory, subscriptions, etc.) justifies the count. It is on the heavy side but still manageable with clear organization.

Completeness5/5

The tool surface is remarkably complete for the apparent domain: exploration (discover_tools, suggest_questions), identifier resolution (resolve_entity), data retrieval (ask_pipeworx, deep_research, entity_profile, compare_entities, recent_changes, validate_claim), prediction market analysis (full suite), memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), and extras (ENS, dependency scan, AI visibility). No obvious gaps exist.

Resources