Skip to main content
Glama

Whiskyhunter

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

A5/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing rate limits ('Rate-limited to 5 per identifier per day'), quota exemption ('doesn't count against your tool-call quota'), and the return-flow behavior ('Filing without an account returns a claim_token; pass it back later...'). Annotations indicate readOnlyHint=false, which is consistent with a write/submit operation.

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 lengthy but every sentence carries distinct information: purpose, exclusions, token mechanics, rate limits, and roadmap impact. It is front-loaded with the core purpose and then flows through usage constraints. No filler or repetition.

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?

Despite lacking an output schema, the description fully explains the return value (claim_token) and the follow-up mechanism to read status/changes. It also covers rate limits, quota, and scope, making it self-sufficient for a 4-parameter tool with a nested context object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds meaningful usage semantics beyond the schema: it explains that claim_token must be passed 'with no other arguments,' and instructs users to describe issues 'in terms of Pipeworx tools/packs' rather than pasting the end-user prompt. This materially improves parameter understanding.

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 verb and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly enumerates the feedback types (bug, feature/data_gap, praise) and differentiates from sibling tools like ask_pipeworx or discover_tools by focusing on reporting issues rather than querying data.

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 conditions for each feedback type and a strong exclusion: 'ONLY for tools served by this Pipeworx connection' with instructions to file elsewhere for other MCP servers. It also explains when to use claim_token to retrieve earlier feedback, leaving no ambiguity about usage.

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

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

Many tools have overlapping purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research all perform research; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker are similar). Agents may struggle to pick the correct tool.

Naming Consistency2/5

Naming is inconsistent: some use snake_case (list_distilleries), others are descriptive (ask_pipeworx, deep_research), and some are branded (pipeworx_feedback). No clear pattern.

Tool Count3/5

33 tools is high but not unreasonable given the broad scope. However, the server name implies a whisky focus, making the count feel excessive for that domain.

Completeness2/5

For the whisky domain suggested by the name, only 3 tools are relevant. The rest are generic or unrelated (Polymarket, npm scanning), leaving significant gaps for whisky-specific tasks.

Resources