Submit Verity Feedback
submit_verity_feedbackReport a reproducible Verity API or MCP bug, missing capability or data-quality issue for human review so you get a tracking receipt once the private report is stored.
Instructions
Submit a reproducible Verity API or MCP bug, missing capability or data-quality report for human review. Requires a developer key (PULSE_API_KEY) or the hosted server, and an enabled feedback service. Include the failed call's requestId when available. Do not send secrets, personal information or conversation transcripts. Saves a private report; does not change prices, start trades or open or merge a PR. Returns a tracking receipt only after storage succeeds.
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": {
"category": "<category>",
"surface": "<surface>",
"expected": "<expected>",
"actual": "<actual>",
"reproduction": "<reproduction>"
},
"name": "submit_verity_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| actual | Yes | What actually happened | |
| symbol | No | Crypto ticker the report is about, when there is one | |
| surface | Yes | The tool or API route the report is about | |
| category | Yes | Kind of report: bug, missing_capability or data_quality | |
| expected | Yes | What you expected to happen | |
| requestId | No | requestId from the response you are reporting, when you have it | |
| observedAt | No | When you saw the problem (ISO-8601 with offset) | |
| reproduction | Yes | Steps to reproduce, 1 to 6 short lines |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| success | No | ||
| feedback | No | ||
| duplicate | No | ||
| requestId | Yes | Identifier for this MCP call; not a signed price field. |