FeedbackCreate
A message to SEC Blast about the API, the MCP server, or the data. Leave out personal data, API keys, and other secrets.
Fields
Nested fields are written with dots; [] marks the items of an array.
| Field | Type | Required | Description |
|---|---|---|---|
category | string | yes | bug: something failed or behaved wrongly. missing_data: SEC data you expected is not there. One of: bug, missing_data, missing_tool, wrong_answer, docs, other. More |
client | object | null | no | The program that sent the feedback, such as the MCP client's name and version. |
client.name | string | yes | — |
client.version | string | null | no | — |
context | object | null | no | Details that help, such as accession, query, and request_id. A JSON object of at most 16 KB. |
message | string | yes | What happened and what you expected. 1 to 4,000 characters after trimming spaces, with no NUL characters. |
source | string | no | Where the feedback comes from. The MCP server sends mcp. One of: api, mcp. |
tool | string | null | no | The MCP tool or API route the feedback is about, such as /v3/filings. At most 100 bytes. |
Field notes
category
missing_tool: no route or tool does what you need. wrong_answer: a value or text is wrong. docs: a description or error message is unclear. other: anything else.
Used by
- Sent to
POST /v3/feedback.
Markdown version: /docs/reference/schemas/feedback-create.md