Skip to main content
Glama

Endoflife

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?

Beyond the sparse annotations (all false), the description discloses rate limiting (5/day), quota behavior (free, doesn't count), the claim_token mechanism for anonymous filing and later status retrieval, and the team's daily digest/SLA. It also warns against pasting end-user prompts, adding behavioral context not visible in 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?

Despite length, the description is front-loaded with the core verb ('Tell...'), then follows a logical order: use cases, exclusions, payload guidance, token flow, SLA, limits. Each sentence adds new information with no repetition or filler.

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?

The tool has no output schema, yet the description explains what an anonymous filing returns (claim_token) and how to later read status. It also covers scope boundaries, rate limits, quota, and roadmap impact, making the description self-sufficient for an agent to decide and invoke correctly.

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?

Although schema coverage is 100%, the description adds operational meaning: the claim_token parameter is contextualized with a call example, and message guidance tells users to describe issues in terms of Pipeworx tools/packs rather than pasting prompts. This goes beyond the field 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 a specific statement of purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly identifies the resource (Pipeworx team/connection) and differentiates from sibling tools by framing it as a feedback channel for Pipeworx-owned tools, not research.

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 enumerates when to use (bug, feature/data_gap, praise) and when not to use: 'if the tool came from a different MCP server... file it with that server instead.' Also provides a test for ambiguity: 'Pipeworx tool names are the ones this connection lists.'

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

All Endoflife 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.9/5.0
Disambiguation2/5

The tool set mixes three near-identical ask_pipeworx variants, multiple overlapping prediction-market tools (polymarket_edges, polymarket_arbitrage, bet_research), and three endoflife tools buried among 31 unrelated Pipeworx tools. This makes distinguishing between tools genuinely confusing, especially when several appear to route to the same underlying data.

Naming Consistency3/5

Most names use lowercase snake_case, but the verb-noun pattern is inconsistent: some are verb_noun (list_products, get_product), others noun_noun (polymarket_edges, bet_research), and a few are bare verbs (recall, forget). The style is readable but does not follow a single predictable convention.

Tool Count2/5

With 34 tools, the count is far too high for a server named 'Endoflife'—only three tools actually relate to endoflife.date tracking. The remaining 31 tools belong to a separate Pipeworx platform, making the tool count an extreme over-scoping for the apparent purpose.

Completeness4/5

The endoflife subset is complete: list_products, get_product, and get_cycle cover the full lifecycle of discovering and retrieving release/support timelines with no dead ends. The broader Pipeworx toolkit also appears fairly comprehensive for its own domain, but the mixed set makes it hard to assess a single coherent surface.

Resources