Skip to main content
Glama

hackernews

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?

Providing rich behavioral context beyond the all-false annotations: the description discloses rate limiting ('Rate-limited to 5 per identifier per day'), quota exemption ('doesn't count against your tool-call quota'), and the claim_token workflow for tracking resolution. This gives agents realistic expectations about side effects and follow-up behavior.

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 longer than average but every sentence conveys a distinct operational fact. It is front-loaded with a clear summary, followed by usage criteria, exclusions, token mechanics, rate limits, and quota. Slightly overpacked, but each piece earns its place.

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?

Since there is no output schema, the description compensates by explaining what the return value contains (claim_token) and how to use it to check status. It addresses the full lifecycle: when to file, what to include, limitations, and follow-up, making the tool fully understandable for an agent.

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%, so the baseline is 3. The description adds value by explaining the claim_token round-trip workflow ('Filing without an account returns a claim_token; pass it back later') and by giving message content guidance ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'), which is beyond the schema descriptions.

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 'Tell the Pipeworx team something is broken, missing, or needs to exist.' — a specific verb and resource that clearly states the tool's purpose. It distinguishes itself from sibling tools like ask_pipeworx by framing itself for bug/feature/praise feedback rather than general queries.

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?

Explicitly states when to use: '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).' It also gives a clear exclusion and alternative: 'if the tool came from a different MCP server... file it with that server instead.'

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

All hackernews 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 have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical, and deep_research also overlaps with them. The Polymarket tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also have fuzzy boundaries. An agent could easily pick the wrong meta-tool or duplicate functionality.

Naming Consistency3/5

All names are snake_case, but the pattern is mixed: some are verb_noun (get_item, list_subscriptions, resolve_entity), some are noun_noun (entity_profile, pipeworx_feedback, polymarket_edges), some are adjective_noun (deep_research, recent_alerts), and a few are single verbs (forget, recall, remember, subscribe). This is readable but not a consistent convention.

Tool Count2/5

With 36 tools, this is far too many for a server named 'hackernews'. The bulk of the tools concern Pipeworx data research, prediction markets, memory, and subscriptions — unrelated to the server's apparent purpose. Many of these could be split into separate servers, and the HN-specific functionality would be better served by a focused set of ~5-8 tools.

Completeness2/5

For the Hacker News domain implied by the server name, the surface is incomplete: there are read-only tools (search, top stories, item/comments) but no write functionality (submit, comment, vote) and no user profile access. The broader data-research capabilities are fairly comprehensive, but that does not rescue the server's coherence given its stated name.

Resources