Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 disclosure burden, and it does state the key scoping constraint (only this Pipeworx connection) plus the consequence of ignoring it (delays). It does not itself explain the token-based follow-up flow or what happens after submission, but the input schema documents the claim_token read-back path, so the gap is small.

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 definition is front-loaded with the action and the routing rule, and every sentence is doing work. The final exclusion clause is longer than strictly necessary but justifies its length by preventing a costly misuse, so it is only mildly verbose.

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 four-parameter intake tool with no output schema, this covers the essential questions: when to file, what to include, and what is out of scope. The one omission is a brief note on what filing returns and how resolution status is tracked, though the schema's claim_token description largely backfills that.

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%, with the enum values, the nested context object, the message length guidance, and the claim_token semantics all documented in-schema. The description adds no parameter-level detail beyond what the schema already provides, so the baseline of 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?

The description opens with a specific verb and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It names the exact categories of input (bug, feature, data_gap, praise), so an agent immediately knows this is a feedback-intake tool rather than a data tool, which is a meaningful distinction among the research/query siblings.

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 explicit use triggers mapped to concrete situations: wrong/stale data (bug), a missing tool (feature/data_gap), and a positive outcome (praise). It also states a hard exclusion — feedback about tools from other MCP servers cannot be fixed here and should be filed with that server — which is exactly the when-not guidance an agent needs to avoid misrouting.

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.