Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "other",
      "message": "Fleet #2184 smoke test: verifying pipeworx_feedback example call returns non-empty."
    },
    "name": "nplg-catalog__pipeworx_feedback"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load. It discloses the important operational boundary (only tools from this Pipeworx server can be fixed here) and warns that mis-filed reports merely delay the caller, but says nothing about rate limits, whether a human replies, or how long resolution takes — the claim_token reply mechanism exists only in the schema.

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?

Dense but well ordered: purpose first, use cases second, the critical scope exclusion last. The parenthetical list of other vendors (Gmail, Splunk, Slack) lengthens the final clause without adding decision-relevant information beyond 'another server'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter feedback tool with no output schema, the description covers purpose, categories, and scope well enough to invoke correctly. It is slightly thin on the claim_token round-trip loop and on what the caller receives after filing, though the schema covers that path.

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

Parameters3/5

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

Schema description coverage is 100%, so the enum meanings, nested pack/tool/vertical context object, and the claim_token return behavior are all already documented in the schema. The description only echoes the specificity guidance ('which tool, what error, what data was missing'), adding marginal meaning beyond structured fields; baseline 3 applies.

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?

Opens with a specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' Combined with the enumerated report categories, an agent immediately knows this is a feedback-filing channel, distinct from the analytical siblings like ask_pipeworx or deep_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 maps scenarios to report types (wrong/stale data = bug, absent tool = feature/data_gap, good outcome = praise) and adds a hard exclusion: only for tools served by this Pipeworx connection, with a directive to file elsewhere for other vendors' connectors. That is the when/when-not/alternative trifecta.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.