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.

Input Schema

TableJSON 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

TableJSON 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.4/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent write. The description adds genuinely new behavioral facts: logged rows are never edited (immutability), and 'reason' is ignored on resolve/reopen. It does not cover auth/permission needs or rate limits, keeping it short of 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?

Three tight sentences plus a related-tools line, front-loaded with the verb and mode split. Every clause carries routing or constraint information; nothing is filler.

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?

With an output schema present, return values need no explanation, and the description compensates for the schema's zero required parameters by spelling out the per-mode required set. It leaves out error/validation behavior (e.g. what happens if id is passed with logging fields), a minor gap.

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 the baseline is 3, but the description adds conditional semantics the schema cannot express: the required-for-logging set (engine, reason, prompt, quote, seenOn), the optional trio, and the id+resolved pairing for state changes. It does not explain enum values, which the schema already handles.

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?

The description opens with a specific verb+resource pair ('Logs a wrong AI answer') and explicitly enumerates the three supported operations (log, resolve, reopen). It also names related siblings (list_wrong_answers, get_buyer_question_answers), so an agent can distinguish it from read-side tools without opening a schema.

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

Usage Guidelines4/5

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

It gives explicit mode-selection rules: which parameters to pass to log versus to resolve/reopen, and which fields are optional or ignored per mode. It lists related tools but does not state when to prefer list_wrong_answers over this one, so it falls short of full when/when-not guidance.

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?