Skip to main content
Glama

NS Pros MCP Gateway

nsi-bg__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": "nsi-bg__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?

With no annotations supplied, the description carries the burden and does disclose the destination (Pipeworx team), the scope boundary (only this connection's tools), and the consequence of misfiling ('only delays you'). It does not state whether submission is asynchronous, whether anyone replies, or any rate limits — and the claim_token read-back mode is only explained in the schema, not the description.

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?

Purpose is front-loaded in the first clause, followed by use cases and then the exclusion rule — a sensible ordering. The final sentence is somewhat long with parenthetical vendor examples ('Gmail, Splunk, Slack, etc.'), but each part contributes to the exclusion boundary.

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 low-risk feedback submission with full schema coverage and no output schema, the description covers intent, categories, and scope adequately. The main residual gap is that the alternate 'read a prior report by claim_token' mode and expected turnaround are left entirely to the schema.

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 every parameter including the type enum, nested context object, message limits, and claim_token token format is already documented in the schema. The description's category phrasing ('bug', 'feature/data_gap', 'praise') largely restates the enum, adding little semantic meaning beyond structured data.

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,' and enumerates the exact categories (bug, feature/data_gap, praise) an agent would file. This clearly separates it from siblings like discover_tools or ask_pipeworx, which serve different intents.

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?

It gives concrete when-to-use triggers (wrong/stale data, missing capability, positive note) and an explicit when-NOT-to-use rule: files originating from another vendor's MCP server should go to that server, not here, because 'we cannot fix it.' That is the strongest form of alternative routing guidance.

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.