Tell AINDEX what went wrong, or right
send_feedbackSend the AINDEX team a short report about AINDEX or this MCP server: an issue (the instructions name a tool that does not exist, a quote failed for a token, a figure looks wrong), an idea, or praise. Before sending: remove anything personal (names, emails, wallet balances tied to a person, anything your human would not post publicly), never include a key or recovery phrase, and show your human the exact draft once and send it only if they agree. Token addresses are fine; shorten transaction hashes to their first 10 characters. One report per client every 5 minutes, so put everything in one. Reports are read by the AINDEX team and never shown to other users; nothing comes back but a reference.
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": {
"kind": "<kind>",
"summary": "<summary>"
},
"name": "send_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | issue: something is wrong or failed. idea: something that should exist. praise: something that worked well. | |
| tool | No | The tool concerned, if any, for example get_token_market. | |
| details | No | What you did, what you expected, what happened instead, and any error text. No personal data. | |
| summary | Yes | One line: what happened. |