Skip to main content
Glama
phuryn

AskOne: Live Q&A and Polls

Related Servers

Alternatives to AskOne: Live Q&A and Polls

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets an external AI agent work inside shared project rooms as a genuine client, handling seven tools that list and fetch projects, read full room state (project, document, recent chat, presence), post chat messages, edit the shared document, create projects, and upvote. Every action happens under a visible agent handle over the same REST and WebSocket endpoints humans use, returning schema-declared structured content and machine-readable error codes so agents can plan multi-step work.
      6 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients like Claude Code to read and post messages in a QRChat agent room without writing curl commands.
      3
      0
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-connected agent sessions across different providers and machines to collaborate in shared rooms, joining via relayable codes to preview and exchange briefs, messages, artifacts, action requests, and a shared read-only working surface. Also serves A2A-speaking agents through a public-room endpoint.
      834 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a chat or voice assistant to drive coding agents running in herdr: it can start an agent on a task, list and watch sessions started anywhere, send follow-ups, answer an agent's questions and approve or refuse its permission prompts. Long-running work is reported back through webhook callbacks so the conversation can continue without blocking.
      MIT

    TDQS

    A4.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct resource and action: rooms are listed/created/opened/closed, questions are read in two clearly differentiated formats (Markdown FAQ vs JSON with ids/paging), surveys are created/closed/results-read, and moderation/answering are separate operations. The two question-read tools could superficially overlap, but their descriptions explicitly state when to use each. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun structure (list_rooms, get_room_qa, create_room, close_survey, moderate_question, etc.). Minor plural/singular variations (list_rooms vs create_room) are conventional and do not harm predictability. The pattern is clear and stable across the entire set.

    Tool Count5/5

    The server exposes 11 tools, squarely within the ideal 3–15 range for a focused Q&A and polling service. Each tool corresponds to a meaningful operation in the room/question/survey lifecycle. There are no redundant or filler tools.

    Completeness4/5

    Core lifecycle coverage is strong: rooms can be created, opened, closed, and listed; questions can be read, moderated, and answered; surveys can be created, closed, and their results retrieved. Minor gaps exist, such as no direct get_room by code (list_rooms must be used), no survey update/delete, and no way to unanswer a question. These are workable limitations rather than critical missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive