AskOne: Live Q&A and Polls

Create a room

create_room

Create a Q&A room in your organization and open it to the audience at once; open=false prepares it so nobody can join until open_room. Use it before a session: it returns the room with its new code, join_url for the audience, projector_url for the wall and host_url for the console; add polls with create_survey. Rooms follow the organization's plan and branding; when all of its open rooms are in use the call fails with room_limit_reached, so close one with close_room first. Needs a token with rooms:write; pass a request_id UUID and resend the same one to retry safely after a lost reply.

Input Schema

Name	Required	Description	Default
`name`	Yes	The room's name, shown to the audience and on the projector; 1 to 80 characters.
`open`	No	true (default) opens the room to the audience at once; false creates it prepared, so nobody can join until open_room.
`moderation`	No	How audience questions are moderated. none: they appear as soon as they are asked. ai (default): an AI hides abuse and spam, and anything it is unsure about waits for review. human: every question waits for a host or moderator to approve it.	ai
`request_id`	No	A UUID you generate; resend the same one with the same fields to retry safely after a lost reply. If omitted, the server generates one and returns it.
`description`	No	Optional notes on what the room is for, seen only by the people who run it, not the audience. Plain text, up to 2,000 characters; blank means none.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 9, 2026

addedInput schema / properties / description / description

Added value: +"Optional notes on what the room is for, seen only by the people who run it, not the audience. Plain text, up to 2,000 characters; blank means none."

addedInput schema / properties / moderation / description

Added value: +"How audience questions are moderated. none: they appear as soon as they are asked. ai (default): an AI hides abuse and spam, and anything it is unsure about waits for review. human: every question waits for a host or moderator to approve it."

addedInput schema / properties / name / description

Added value: +"The room's name, shown to the audience and on the projector; 1 to 80 characters."

addedInput schema / properties / open / description

Added value: +"true (default) opens the room to the audience at once; false creates it prepared, so nobody can join until open_room."

addedInput schema / properties / request_id / description

Added value: +"A UUID you generate; resend the same one with the same fields to retry safely after a lost reply. If omitted, the server generates one and returns it."

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"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "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",
+    "join_url",
+    "projector_url",
+    "host_url",
+    "request_id"
+  ],
+  "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?

Annotations only declare write/non-destructive/open-world, but the description adds substantial behavioral context: the four URLs returned (code, join_url, projector_url, host_url), the room_limit_reached failure mode, the required rooms:write token scope, and the request_id retry contract after a lost reply. This is exactly the extra disclosure annotations cannot provide.

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 with purpose, then returns, error handling, auth, and retry guidance in that order. It is dense but every clause carries decision-relevant information, with no filler or repetition of the title.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the key URLs. Combined with auth requirements, the limit error, and idempotent-retry guidance, an agent has everything needed to call this correctly on the first try.

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 explains name, open, moderation, request_id, and description in detail; the description largely restates the open and request_id semantics. It adds only marginal cross-parameter context (retry behavior tied to room creation), so the baseline 3 applies.

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 and resource with scope: 'Create a Q&A room in your organization.' It immediately distinguishes the tool from siblings by naming open_room, close_room, and create_survey in context, so an agent knows this is the creation step in a room lifecycle.

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 says when to use it ('before a session'), what to do instead when the room limit is hit ('close one with close_room first'), and how it relates to alternatives like open_room for deferred opening and create_survey for follow-up content. Both the when and the when-not are covered.

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.