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 Scout. 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 one of two Scout tools that reach the network (a load with semantic: true provisions the embedding model): it sends the authored text off the machine and files it as a public issue. It is off unless a release build runs with telemetry on, so a build with no feedback endpoint sends nothing. GLIDER_FEEDBACK=0 disables the tool; --no-telemetry and DO_NOT_TRACK=1 also disable it. At most 5 distinct reports are attempted per session. Retries with the original reportId use no additional report quota. The tool asks the agent to tell the user what it sent; whether a call runs without a prompt is decided by the MCP client approval settings, not by the server. The public issue carries the report id and never an install or session identifier.

Parameters

Name	Type	Required	Description
responseDetail	string	No	compact returns results and actionable state. full returns the original envelope with timing, revision, and display annotations. Default: `"compact"`
category	string	Yes	Report category: missing-capability, bad-output, error, or praise.
message	string	Yes	What you tried to do and could not do, abstractly. 1 to 500 characters. The tool refuses code, paths, source and config file names, secrets, and stack traces, and names the reason. Do not name private symbols.
relatedTool	string	No	The scout tool the report is about, for example find. Optional. 1 to 64 lowercase letters, digits, or underscores.
harness	string	No	Coding agent and its version, for example "claude-code 2.1.0". Optional. Letters, digits, spaces, and . _ + - only.
model	string	No	Model that wrote the report, for example "claude-opus-5". Optional. Same character rules as harness.
otherMcpServers	json	No	Other MCP servers in the session, only when they matter to the report. JSON array of up to 8 names of lowercase letters, digits, - and _.
reportId	string	No	Available in Scout 4.2.0. Optional GUID returned for a report in this server session. Reuse it with the original authored fields within 29 days to retry that report.

Examples

Replace sample paths and symbol keys with values from your workspace.

Report a missing capability after an update and a duplicate search

Arguments 
{
  "category": "missing-capability",
  "message": "no search mode returns callers of a symbol",
  "relatedTool": "find"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "send_feedback",
    "arguments": {
      "category": "missing-capability",
      "message": "no search mode returns callers of a symbol",
      "relatedTool": "find"
    }
  }
}

Illustrative response 
{
  "status": "filed",
  "reportId": "3f9c2b1e-8d4a-4c6f-9a21-5b7e0d1c2f34",
  "issueUrl": "https://github.com/glidermcp/glidermcp.com/issues/123",
  "report": {
    "category": "missing-capability",
    "message": "no search mode returns callers of a symbol",
    "relatedTool": "find",
    "harness": null,
    "model": null,
    "otherMcpServers": []
  },
  "product": {
    "product": "scout",
    "productVersion": "3.1.0",
    "os": "macos",
    "arch": "arm64",
    "runtime": "native"
  },
  "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

Arguments 
{
  "reportId": "3f9c2b1e-8d4a-4c6f-9a21-5b7e0d1c2f34",
  "category": "missing-capability",
  "message": "no search mode returns callers of a symbol",
  "relatedTool": "find"
}

Full MCP request

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 search mode returns callers of a symbol",
      "relatedTool": "find"
    }
  }
}

Response Notes

Returns the status of the report: filed, duplicate, queued, or unconfirmed. It also returns the report id and the public issue URL. 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 with data.refused { reason, field, detail }, so the agent can rewrite the named field. A disabled tool returns success:false with the reason it sends nothing, and server_status reports the same state under feedback. An unconfirmed status means delivery or publication was not confirmed. The report may or may not have been published. 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.