What inputs does submit_feedback accept?

category ("bug" | "feature_request" | "experience" | "data_quality" | "other", required): What kind of feedback this is: 'bug' (something broke), 'feature_request' (something missing), 'experience' (UX / clarity / docs), 'data_quality' (a wrong/missing/stale figure), or 'other'. message (string, required): The feedback body (1–4000 chars). Be specific: what you expected, what happened, and any reproduction steps. May contain the user's own words — it is stored for triage and never used for arithmetic. subject (string, optional): Optional short title (≤140 chars) summarizing the feedback. severity ("low" | "medium" | "high", optional): Optional impact classification: 'low', 'medium', or 'high'. surface ("mcp" | "workspace" | "sdk" | "dashboard" | "api", optional): Optional product surface the feedback concerns: 'mcp', 'workspace', 'sdk', 'dashboard', or 'api'. context (object, optional): Optional free-form context object (stored as JSON), e.g. { tool: 'get_company_fundamentals', ticker: 'AAPL', request_id: 'abc123' }. Avoid secrets. idempotency_key (string, optional): Optional client-supplied key (1–64 chars). For authenticated callers, reusing the same key files the feedback exactly once — safe to retry on a network error. Ignored for guest/sample callers (no account to scope dedup to). sentiment ("positive" | "negative" | "correction", optional): Optional sentiment of this feedback: 'positive' (worked well), 'negative' (something was wrong), or 'correction' (you are supplying the right value). reason ("wrong_number" | "bad_citation" | "missing_data" | "wrong_company" | "formatting" | "hallucinated_fact" | "tool_error" | "coverage_gap" | "other", optional): Optional structured error-mode reason: 'wrong_number', 'bad_citation', 'missing_data', 'wrong_company', 'formatting', 'hallucinated_fact', 'tool_error', 'coverage_gap', or 'other'. target_type ("chat_message" | "report" | "thesis" | "claim" | "tool_call" | "schema" | "other", optional): Optional kind of artifact the feedback targets: 'chat_message', 'report', 'thesis', 'claim', 'tool_call', 'schema', or 'other'. target_id (string, optional): Optional id of the artifact this feedback targets (e.g. a report or thesis id). request_id (string, optional): Optional `_meta` request id of the turn that produced the artifact, for correlation. fact_id (string, optional): Optional disputed `fact_id` (for wrong_number / bad_citation feedback). expected_value (string, optional): Optional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data.

Which Valuein plans include submit_feedback?

Available on every plan, including the free tier with no account. Not point-in-time safe.

Discovery

Submit Feedback

submit_feedback

Sample and above

File product feedback to the Valuein team — a bug, feature request, experience note, or data-quality issue — directly from the agent surface. Available on EVERY tier including guest/sample (no token required), so an agent can report a rough edge in-band without the human leavi...

Example Call

example_call.pypython

# Using the Valuein MCP server from Python (via MCP SDK)# Or call directly from Claude / Cursor after setup result = await client.call_tool(    "submit_feedback",    arguments={    "category": "bug",    "message": "EXAMPLE"})print(result)

Direct tool call:submit_feedback(...)

Inputs

Parameter	Type	Required	Description
`category`	"bug" \| "feature_request" \| "experience" \| "data_quality" \| "other"	required	What kind of feedback this is: 'bug' (something broke), 'feature_request' (something missing), 'experience' (UX / clarity / docs), 'data_quality' (a wrong/missing/stale figure), or 'other'.
`message`	string	required	The feedback body (1–4000 chars). Be specific: what you expected, what happened, and any reproduction steps. May contain the user's own words — it is stored for triage and never used for arithmetic.
`subject`	string	optional	Optional short title (≤140 chars) summarizing the feedback.
`severity`	"low" \| "medium" \| "high"	optional	Optional impact classification: 'low', 'medium', or 'high'.
`surface`	"mcp" \| "workspace" \| "sdk" \| "dashboard" \| "api"	optional	Optional product surface the feedback concerns: 'mcp', 'workspace', 'sdk', 'dashboard', or 'api'.
`context`	object	optional	Optional free-form context object (stored as JSON), e.g. { tool: 'get_company_fundamentals', ticker: 'AAPL', request_id: 'abc123' }. Avoid secrets.
`idempotency_key`	string	optional	Optional client-supplied key (1–64 chars). For authenticated callers, reusing the same key files the feedback exactly once — safe to retry on a network error. Ignored for guest/sample callers (no account to scope dedup to).
`sentiment`	"positive" \| "negative" \| "correction"	optional	Optional sentiment of this feedback: 'positive' (worked well), 'negative' (something was wrong), or 'correction' (you are supplying the right value).
`reason`	"wrong_number" \| "bad_citation" \| "missing_data" \| "wrong_company" \| "formatting" \| "hallucinated_fact" \| "tool_error" \| "coverage_gap" \| "other"	optional	Optional structured error-mode reason: 'wrong_number', 'bad_citation', 'missing_data', 'wrong_company', 'formatting', 'hallucinated_fact', 'tool_error', 'coverage_gap', or 'other'.
`target_type`	"chat_message" \| "report" \| "thesis" \| "claim" \| "tool_call" \| "schema" \| "other"	optional	Optional kind of artifact the feedback targets: 'chat_message', 'report', 'thesis', 'claim', 'tool_call', 'schema', or 'other'.
`target_id`	string	optional	Optional id of the artifact this feedback targets (e.g. a report or thesis id).
`request_id`	string	optional	Optional `_meta` request id of the turn that produced the artifact, for correlation.
`fact_id`	string	optional	Optional disputed `fact_id` (for wrong_number / bad_citation feedback).
`expected_value`	string	optional	Optional caller-asserted correct value, in your own words. Stored verbatim for triage — NEVER computed or trusted as data.

Output Fields

feedbackacknowledgment

Example Response

Illustrative

response.jsonjson

{  "feedback": null,  "acknowledgment": null}

Shape only — field names match the live schema; values are placeholders, not real filings. See MCP server for the structured response shape.

Notes

Available from the Sample plan and above.

Try this tool

Get token All tools

CategoryDiscovery

PIT-safeNo

Min planSample

Inputs14 (2 required)

Plan Access

Sample (guest)

Available

Benchmark (token)

Available

Pro

Available

Institutional

Available

Related Tools

search_companies

Search Companies

get_company_fundamentals

Company Fundamentals

get_valuation_metrics

Valuation Metrics

get_financial_ratios

Financial Ratios

Resources

Point-in-Time methodology →Parquet schema reference →Bulk Data API reference →Python SDK guide →

Index names are trademarks of their owners; Valuein is not affiliated with or endorsed by any index provider.