AskOne: Live Q&A and Polls

Mark a question answered

answer_question

DestructiveIdempotent

Mark an approved question as answered, optionally with a written answer of up to 1,000 characters that the audience sees under it. Use it as the host answers during or after a session; without answer, any written comment already saved is kept. Only approved or already-answered questions qualify, so approve a waiting one first with moderate_question. Get the question id from get_room_qa. It cannot be marked unanswered through these tools. Returns the question's id, status and answer. Needs rooms:write.

Input Schema

Name	Required	Description
`code`	Yes	The room's six-character code (letters and digits, any case), from list_rooms or create_room.
`answer`	No	Optional written answer the audience sees under the question: plain text, up to 1,000 characters. Omit it, or send blank text, to mark the question answered and keep any comment already saved.
`question_id`	Yes	The question's id, a UUID from the questions in get_room_qa's structured result.

Output Schema

Name	Required	Description	Default
`room`	Yes
`host_url`	Yes
`join_url`	Yes
`question`	Yes
`projector_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 9, 2026

addedInput schema / properties / answer / description

Added value: +"Optional written answer the audience sees under the question: plain text, up to 1,000 characters. Omit it, or send blank text, to mark the question answered and keep any comment already saved."

addedInput schema / properties / code / description

Added value: +"The room's six-character code (letters and digits, any case), from list_rooms or create_room."

addedInput schema / properties / question_id / description

Added value: +"The question's id, a UUID from the questions in get_room_qa's structured result."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "host_url": {
+      "type": "string"
+    },
+    "join_url": {
+      "type": "string"
+    },
+    "projector_url": {
+      "type": "string"
+    },
+    "question": {
+      "properties": {
+        "answer": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "answered_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "status": {
+          "description": "pending: awaiting review; approved: visible; hidden: shown to nobody; answered: marked answered.",
+          "enum": [
+            "pending",
+            "approved",
+            "hidden",
+            "answered"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "status",
+        "answer",
+        "answered_at"
+      ],
+      "type": "object"
+    },
+    "room": {
+      "properties": {
+        "closed_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "code": {
+          "type": "string"
+        },
+        "counts": {
+          "properties": {
+            "active": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "answered": {
+              "description": "Included in questions.",
+              "minimum": 0,
+              "type": "integer"
+            },
+            "participants": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "pending": {
+              "minimum": 0,
+              "type": "integer"
+            },
+            "questions": {
+              "description": "Approved and answered questions.",
+              "minimum": 0,
+              "type": "integer"
+            }
+          },
+          "required": [
+            "questions",
+            "pending",
+            "answered",
+            "participants",
+            "active"
+          ],
+          "type": "object"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "description": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "name": {
+          "type": "string"
+        },
+        "opened_at": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "description": "prepared: not joinable yet; open: live; closed: not joinable, content stays readable.",
+          "enum": [
+            "prepared",
+            "open",
+            "closed"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "name",
+        "status",
+        "description",
+        "created_at",
+        "opened_at",
+        "closed_at",
+        "counts"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "room",
+    "question",
+    "join_url",
+    "projector_url",
+    "host_url"
+  ],
+  "type": "object"
+}

AddedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description discloses the permission requirement ('rooms:write'), the eligibility constraint (only approved/already-answered questions), the no-op behavior when answer is omitted, and the irreversibility. Nothing here contradicts the annotations.

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?

Four dense sentences, front-loaded with the action and its scope, followed by prerequisites, provenance, and constraints. Every sentence carries information an agent needs; none is filler.

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

Completeness5/5

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

For a mutation tool with a rich annotation set and an existing output schema, this description covers the full picture: prerequisites, permissions, idempotent behavior, and irreversibility. Nothing material is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents code, answer, and question_id fully. The description restates the 1,000-character audience-visible answer and the keep-existing-comment behavior, which the schema also covers. Baseline 3 is appropriate since the description adds little beyond structured fields.

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 precise verb+resource ('Mark an approved question as answered') and immediately qualifies scope with 'approved'. An agent can distinguish it from nearby siblings such as moderate_question and get_room_qa without opening their schemas.

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?

Gives explicit when-to-use ('as the host answers during or after a session'), the prerequisite ('approve a waiting one first with moderate_question'), the source of the id ('get_room_qa'), and an explicit limitation ('It cannot be marked unanswered through these tools'). This is exactly the routing information an agent needs.

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

All AskOne: Live Q&A and Polls 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.