Suggest a roadmap item
r3_roadmap_suggestSuggest a feature for R3's public roadmap, in the user's name and naming you (your agent key or app connection). It is HELD until R3's team approves it: not public, not votable, until then. r3_roadmap_list shows whether an item already covers it (r3_roadmap_upvote votes for that one instead). A good suggestion says what the feature lets a person do and why (what was being built when it was missed). Something broken rather than missing is r3_bug_report's. Rate-limited per agent key or app connection (a few a day). Needs the roadmap:suggest right.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"description": "<description>"
},
"name": "r3_roadmap_suggest"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | One line naming the feature, e.g. "Per-wheel tyre grip in the Inspector". | |
| category | No | Where it belongs; "other" when unsure. | |
| description | Yes | What it lets a person do, and why it is needed. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| title | Yes | ||
| answer | Yes | This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance. | |
| approved | Yes |