send_feedback
[feedback]
Sends feedback and product facts as a public GitHub issue. First search open and closed issues in glidermcp/glidermcp for your exact problem using abstract, public terms. Confirm each duplicate concerns TGlider. Update to the latest product version. Restart the server. Retry the affected operation. If a duplicate exists, use the existing issue. Call send_feedback only if the problem persists after the update and no duplicate exists.
Before you use this tool
This is the one TGlider tool that publishes authored text off the machine, and the result is a public GitHub issue. It sends the report the agent wrote plus the product, version, OS, architecture, runtime, an anonymous install id, and the anonymous session id telemetry uses. It never sends source, file contents, or workspace paths. Set GLIDER_FEEDBACK=0 to turn it off on its own; --no-telemetry and DO_NOT_TRACK=1 turn off both channels. Whether a tool runs without asking you is governed by your MCP client approval settings, not by this server.
Try it locally in the TGlider playground
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| category | string | Yes | One of missing-capability, bad-output, error, or praise. |
| message | string | Yes | What the agent tried to do and could not, in abstract words. 1 to 500 characters. |
| relatedTool | string | No | The TGlider tool the report is about. Optional. |
| harness | string | No | Coding agent and its version. Optional. |
| model | string | No | Model that wrote the report. Optional. |
| otherMcpServers | json | No | Other MCP servers in the session, up to 8, only when they matter. |
| reportId | string | No | Optional GUID returned for a report in this server session. Reuse it with the original authored fields within 29 days to retry that report. Unreleased parameter. Available in development builds. |
Examples
Replace sample paths and symbol keys with values from your workspace.
Report a missing capability after an update and a duplicate search
{
"category": "missing-capability",
"message": "no tool reports the export surface of a package",
"relatedTool": "find_code"
}Full MCP request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "send_feedback",
"arguments": {
"category": "missing-capability",
"message": "no tool reports the export surface of a package",
"relatedTool": "find_code"
}
}
}{
"success": true,
"data": {
"status": "filed",
"reportId": "3f9c2b1e-8d4a-4c6f-9a21-5b7e0d1c2f34",
"issueUrl": "https://github.com/glidermcp/glidermcp.com/issues/123",
"report": {
"category": "missing-capability",
"message": "no tool reports the export surface of a package",
"relatedTool": "find_code"
},
"product": {
"product": "tglider",
"productVersion": "0.9.0",
"os": "macos",
"arch": "arm64",
"runtime": "22.14.0"
},
"remainingThisSession": 4,
"hints": {
"nextSteps": [
"Show the user the issue URL; the report is public there."
]
}
}
}Retry an unconfirmed report with its returned ID in the same session
{
"reportId": "3f9c2b1e-8d4a-4c6f-9a21-5b7e0d1c2f34",
"category": "missing-capability",
"message": "no tool reports the export surface of a package",
"relatedTool": "find_code"
}Full MCP request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "send_feedback",
"arguments": {
"reportId": "3f9c2b1e-8d4a-4c6f-9a21-5b7e0d1c2f34",
"category": "missing-capability",
"message": "no tool reports the export surface of a package",
"relatedTool": "find_code"
}
}
}Response Notes
Returns the status of the report: filed, duplicate, queued, failed, or unconfirmed. A sent or unconfirmed result carries the report id. A disabled or refused call carries no report ID. A filed or duplicate result carries the public issue URL. A queued or failed result carries null. An unconfirmed result omits the field. A failed status means the server stored the report but could not publish it, and answers success:false. An unconfirmed status means delivery remains uncertain. Network errors, timeouts, cancellation, and unexpected responses can occur after storage. It repeats the authored fields exactly as they were sent. It adds the public product facts, the number of reports left in this session, and next steps. The result never carries an install or session identifier. A refused report returns success:false naming the field to rewrite. A disabled tool returns success:false with the reason it sends nothing, and server_status reports the same state under feedback. To retry an unconfirmed report, pass its returned reportId and all original authored fields. Category and message remain required. The fields must match their original normalized values. The server resends the original report. It refuses unknown IDs, IDs from another session, and changed fields before submission. Retry IDs expire after 29 days or when the server session ends. Retries do not extend this limit. Clock changes can end availability earlier. An expired ID returns retry_expired without submission or quota use. Do not submit an expired report under a new ID.