Skip to main content
Glama

NS Pros MCP Gateway

noirlab-datalab__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": "noirlab-datalab__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.5/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 full burden and does meaningful work: it discloses that the report reaches the Pipeworx team, that out-of-scope reports will not be acted on, and that filing returns a token used to read back status and eventual resolution. It does not cover rate limits, whether reports are private, or what the immediate filing response contains, which keeps it short of a 5.

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 and the three use cases are front-loaded in the first sentence, with the scope restriction second — correct ordering for a router-like decision. The second sentence is clause-heavy and slightly padded by the vendor examples ("Gmail, Splunk, Slack, etc."), but each part still earns its place by preventing wasted reports.

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?

Four optional parameters with full schema documentation, no output schema, and no annotations — the description covers purpose, trigger conditions, scope boundaries, and the token follow-up loop, which is what an agent needs to call it correctly. It leaves unstated whether `message` is effectively required in practice, a minor gap given every parameter is marked optional.

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

Parameters4/5

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

Schema coverage is 100% and the enum values for `type` are already documented per-value, so the baseline is 3. The description adds real meaning beyond the schema by tying the enum choices to concrete triggering situations and by framing `claim_token` as the follow-up path for an earlier report rather than a generic identifier.

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+resource pair: "Tell the Pipeworx team something is broken, missing, or needs to exist." It then enumerates the concrete report categories (bug, feature/data_gap, praise), which cleanly separates this feedback channel from every sibling tool that queries or analyzes data.

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 situations (wrong/stale data → bug, missing catalog tool → feature/data_gap, surprising success → praise). It also states a hard exclusion with a redirect: reports about tools from other MCP servers "only delay you; file it with that server instead." When-to-use, when-not-to-use, and the alternative are all present.

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.