Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It discloses the important scope constraint and who receives the report, but it says nothing about what filing returns, whether a follow-up is needed, rate limits, or that report content is transmitted to the vendor team. The reply/polling mechanism is only explained inside the claim_token parameter description in the schema, not in the description body.

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 purpose is front-loaded in the first sentence and the exclusion follows in the second, so an agent gets the gist immediately. The parenthetical catalog of other vendors' connectors is slightly verbose but reinforces the scoping rule, so little is wasted.

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 4-parameter, all-optional tool with 100% schema coverage, no annotations, and no output schema, the description covers routing, scope, and category selection well. The remaining gap is the post-filing lifecycle (token return and later retrieval), which is partially recoverable from the schema but ideally would be mentioned up front.

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%, and the `type` enum already documents all five values, so the schema fully defines the parameters. The description's category mapping in prose largely restates the enum semantics rather than adding new meaning. Baseline 3 applies when the schema does the heavy lifting.

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 states a concrete verb and resource ("Tell the Pipeworx team something is broken, missing, or needs to exist") and enumerates the four supported report intents. It also scopes the tool to tools served by this Pipeworx connection, which is exactly the distinction an agent needs given that a `*__pipeworx_feedback` tool exists under every pack.

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 trigger conditions mapped to each category: wrong or stale data -> bug, a missing tool -> feature, unexposed data -> data_gap, something that worked well -> praise. It also gives an explicit exclusion plus a redirect: if the tool came from another vendor's MCP server, file with that server instead because this channel cannot fix it.

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.