Skip to main content
Glama

AskOne: Live Q&A and Polls

by io.github.phuryn
OverviewDiscussionsAdmin

List rooms

list_rooms
Read-onlyIdempotent

List your organization's rooms, newest first. Each has its six-character code, status (prepared, open or closed) and counts: questions (approved and answered), pending (waiting for review), answered, participants and active. Use it to find the code the room tools take; create_room needs none and returns a new room's code. To reach older rooms, call again with cursor set to the returned next_cursor until next_cursor is null. Read-only; any AskOne API token can call it.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return in this page, from 1 to 100. Default 50.
cursorNonext_cursor from the previous page, passed unchanged; omit for the first page.

Output Schema

NameRequiredDescriptionDefault
roomsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"next_cursor from the previous page, passed unchanged; omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return in this page, from 1 to 100. Default 50."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "next_cursor": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "rooms": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "rooms",
+    "next_cursor"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), and the description reinforces the read-only nature while adding genuinely new context: any AskOne API token suffices, and the paging loop terminates at a null next_cursor. It stops short of describing failure modes or rate limits, so it is strong but not exhaustive.

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

Conciseness4/5

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

The sentence order is well front-loaded: purpose, then returned fields, then usage vs. sibling, then pagination and auth. It is slightly heavy in enumerating result fields (statuses and counts) that the output schema already provides, which is a small redundancy rather than 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?

With an output schema present the description does not need to explain return values, yet it adds the pieces an agent genuinely needs: how to identify a room (six-character code), how to page, and that the tool is read-only and broadly authorized. Nothing required to call it correctly is missing.

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; the description rises above it by explaining cursor semantics as a loop ("call again with cursor set to the returned next_cursor until next_cursor is null"), which is more actionable than the schema's "passed unchanged" note. The limit parameter is left entirely to the schema.

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 ("List your organization's rooms") plus ordering ("newest first") and the fields returned. It also names the sibling it differs from ("create_room needs none and returns a new room's code"), so an agent can separate it from create_room/open_room/close_room without opening 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?

Explicitly says when to use it ("Use it to find the code the room tools take") and contrasts that with create_room, which does not need a code. Pagination behavior is also prescribed: call again with cursor set to next_cursor until next_cursor is null.

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 toolsInspect
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