Skip to main content
Glama
Sign In
askboard-mcp

askboard-mcp

by qinsehm1128
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ask the user via a web form

ask_user

Collect multiple answers from a user through an interactive web form, supporting single-choice, multi-choice, and free-text questions, and return the structured responses.

Instructions

Show the user an interactive web form (opens in their browser) to collect answers, instead of asking one question at a time in chat. Pass a list of questions; each can be single-choice, multi-choice, or free text, and can allow a custom write-in. The call blocks until the user submits, then returns their structured answers. Use this whenever you have a task list, a review checklist, or several questions for the user to decide on at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fields": "<fields>"
    },
    "name": "ask_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
introNoShort paragraph explaining the request
titleNoHeading shown at the top of the form
fieldsYesThe questions to ask

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that the call blocks until the user submits, returns structured answers, opens in a browser, and supports various question types with an optional custom write-in. This provides comprehensive behavioral context.

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?

The description is four sentences long, front-loaded with the primary purpose, and every sentence adds meaningful information. There is no redundancy or fluff, and it is well-structured with the usage tip at the end.

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?

Given the schema fully documents parameters and the description covers when to use the tool, its blocking behavior, and return type, it is complete for this interactive form tool. No output schema is needed to understand what is returned.

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 all parameters are already documented. The description adds some context about form behavior and 'structured answers' but does not significantly deepen parameter-level meaning beyond what the schema provides. A baseline of 3 is appropriate.

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?

The description clearly states the tool shows an interactive web form to collect answers, contrasting with asking in chat. It specifies the resource (form) and action (ask/collect), and differentiates from siblings (open_dashboard, get_updates) which are unrelated.

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?

Explicit guidance is provided: 'Use this whenever you have a task list, a review checklist, or several questions for the user to decide on at once.' It also notes when not to use it ('instead of asking one question at a time in chat'), giving a clear alternative.

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