Mark

Save Wrong Answer

save_wrong_answer

Logs a wrong AI answer, or resolves or reopens one. To log: pass engine, reason, prompt, quote and seenOn; question, market and note are optional. To resolve or reopen: pass id and resolved: true or false. Logged rows are never edited. Related: list_wrong_answers, get_buyer_question_answers, save_idea (wrongAnswerId).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_wrong_answer"
  }
}

Input Schema

Name	Required	Description
`id`	No	Existing wrong answer id. Pass with resolved.
`note`	No	Why it's wrong, e.g. invented pricing.
`quote`	No	What the engine said, the wrong part.
`engine`	No	Where it was seen.
`market`	No	Active market id or exact name.
`prompt`	No	What was asked.
`reason`	No	Why it's wrong. Required to log; ignored on resolve or reopen.
`seenOn`	No	YYYY-MM-DD.
`question`	No	Active buyer question id, or its exact text.
`resolved`	No	With id: true marks it resolved, false reopens it.

Output Schema

Name	Required	Description	Default
`appUrl`	Yes
`wrongAnswer`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 20, 2026

addedInput schema / properties / reason

Added value: +{
+  "description": "Why it's wrong. Required to log; ignored on resolve or reopen.",
+  "enum": [
+    "wrong_fact",
+    "competitor_instead",
+    "negative_framing",
+    "outdated",
+    "missing_citation",
+    "other"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / wrongAnswer / properties / createdById / description
```
Added value: +"Null for weekly_check."
```
changedOutput schema / properties / wrongAnswer / properties / createdById / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / wrongAnswer / properties / quote / description

Previous value: -"What the engine said, as the member pasted it."New value: +"What the engine said: as the member pasted it, or the whole answer for weekly_check."

addedOutput schema / properties / wrongAnswer / properties / reason

Added value: +{
+  "enum": [
+    "wrong_fact",
+    "competitor_instead",
+    "negative_framing",
+    "outdated",
+    "missing_citation",
+    "other"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / wrongAnswer / properties / source

Added value: +{
+  "description": "weekly_check: the weekly check filed it because the answer named an active competitor and not the brand.",
+  "enum": [
+    "member",
+    "weekly_check"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / wrongAnswer / required

Previous value: -[
-  "id",
-  "engine",
-  "prompt",
-  "quote",
-  "seenOn",
-  "note",
-  "question",
-  "market",
-  "createdById",
-  "createdAt",
-  "resolvedAt",
-  "resolvedById"
-]New value: +[
+  "id",
+  "engine",
+  "reason",
+  "source",
+  "prompt",
+  "quote",
+  "seenOn",
+  "note",
+  "question",
+  "market",
+  "createdById",
+  "createdAt",
+  "resolvedAt",
+  "resolvedById"
+]

AddedOct 8, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds real context beyond annotations: 'Logged rows are never edited' clarifies that resolution flips state rather than mutating content, and 'reason ... ignored on resolve or reopen' prevents a silent-argument mistake. Annotations cover the safety profile (destructive=false), so this extra immutability policy is the value-add; only the lack of any note about what a resolve returns or whether ids must exist keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded verb, then mode-split sentences, then related tools. No filler; every clause carries a distinct instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter dual-mode tool with an output schema, the description covers both modes and the conditional required set. It does not address precedence when both an id and log fields are supplied, which is the one ambiguity an agent could hit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but the description adds information the schema cannot express: required=0 in the schema, yet five parameters are conditionally required to log, and the description states that explicitly along with which are optional. It also clarifies the id+resolved pairing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Logs a wrong AI answer') and immediately names the two additional modes (resolve, reopen). An agent can distinguish this from list_wrong_answers or save_idea without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly branches usage: 'To log: pass engine, reason, prompt, quote and seenOn' vs 'To resolve or reopen: pass id and resolved: true or false'. It also names related tools (list_wrong_answers, get_buyer_question_answers, save_idea's wrongAnswerId), giving clear routing context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?