Skip to main content
Glama
phuryn

AskOne: Live Q&A and Polls

by phuryn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Mark a question answered

answer_question
DestructiveIdempotent

Mark an approved audience question as answered, optionally adding a written reply of up to 1,000 characters visible to participants.

Instructions

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_questions. It cannot be marked unanswered through these tools. Returns the question's id, status and answer. Needs rooms:write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesSix-character room code, for example ABC234
answerNoOptional written answer, up to 1,000 characters of plain text
question_idYesQuestion id from get_room_questions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint/idempotent), it discloses the irreversibility (

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?

Front-loaded with the action and effect, then prerequisites, then provenance of the id, then return fields. Five sentences is dense but each carries a distinct, non-redundant fact.

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 no output schema, the description compensates by naming the return fields (id, status, answer), and it also covers the permission requirement (rooms:write) and the irreversibility constraint. An agent has everything needed to call and interpret it.

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 real meaning: the answer is optional and audience-visible, is capped at 1,000 characters, and omitting it preserves an existing written comment rather than clearing it.

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+resource+precondition ('Mark an approved question as answered') and distinguishes itself from siblings by naming moderate_question and get_room_questions. An agent can tell exactly what changes and on which entity without opening the schema.

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 context ('as the host answers during or after a session'), names the prerequisite ('Only approved or already-answered questions qualify, so approve a waiting one first with moderate_question'), and routes the agent to get_room_questions for the required id.

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

Deploy Server

Other Tools