pipeworx_feedback
ActiveTool of mcp-semanticscholar
declared in 0.1.0
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). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
Parameters schema
{
"type": "object",
"required": [
"type",
"message"
],
"properties": {
"type": {
"enum": [
"bug",
"feature",
"data_gap",
"praise",
"other"
],
"type": "string",
"description": "bug = 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."
},
"context": {
"type": "object",
"properties": {
"pack": {
"type": "string",
"description": "Pack slug (e.g., \"fred\")"
},
"tool": {
"type": "string",
"description": "Tool name (e.g., \"fred_get_series\")"
},
"vertical": {
"type": "string",
"description": "Vertical (e.g., \"housing\")"
}
},
"description": "Optional structured context: which tool, pack, or vertical this relates to."
},
"message": {
"type": "string",
"description": "Your feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max."
}
}
}Parent server
mcp-semanticscholar
https://github.com/pipeworx-io/mcp-semanticscholar
2/7 registries