Skip to main content
Glama
jens-duttke

mcp-popup-ui

by jens-duttke

ask_user_multiple

Present a popup to let users select one or more options from a list, enabling multi-choice input for preferences, features, or tags.

Instructions

Ask the user to choose ONE OR MORE options from a list. Use this tool instead of listing options in your text response whenever the user can select multiple items.

WHEN TO USE THIS TOOL:

  • You are about to list items and ask "which ones do you want?" or "select all that apply"

  • The user can pick multiple non-exclusive options (e.g., "Which features to include?", "Which files to modify?", "What languages do you know?")

  • You need to gather multiple preferences at once

EXAMPLES OF WHEN TO USE:

  • "Which features do you want?" → Use this tool

  • "Select the files to include" → Use this tool

  • "What integrations should I add?" → Use this tool

  • "Pick all applicable tags" → Use this tool

⚠️ CRITICAL: Each parameter MUST be passed SEPARATELY. Do NOT combine them!

❌ WRONG (options contains title/description - WILL FAIL): options: [{"label": "A"}, {"label": "B"}], "title": "...", "description": "..."

✅ CORRECT (each parameter separate): options: [{"label": "A"}, {"label": "B"}] title: "Select features" description: "Choose all that apply"

PARAMETERS:

  • options (REQUIRED): Array of objects, each with "label" (required) and optional "description", "recommended"

  • title (optional): String displayed above options

  • description (optional): String displayed below title

  • min_selections (optional): Minimum selections required

  • max_selections (optional): Maximum selections allowed

  • allow_other (optional): Boolean to allow custom input

The tool opens a popup in the user's browser and waits for their selections. If allow_other is true, users can add custom text if predefined options don't fit. Returns an array of selected options, or indicates if the user skipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional title displayed above the selection. Use to provide context or ask a question.
optionsYesList of options for the user to choose from. Each option must have a label property. Use description for additional context (pros/cons, features). The user will see these in a popup and can select multiple.
allow_otherNoIf true, adds an "Other" option that allows the user to enter custom text. The "Other" text will be included in the results array if selected.
descriptionNoOptional description text displayed below the title. Use for additional instructions or clarification.
other_labelNoCustom label for the "Other" option. Only used when allow_other is true.Other

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhether the user submitted selections, skipped, or requested an explanation for an option
commentsNoAdditional comments provided by the user (only present if allow_comments was true and user entered text)
selectionsNoThe selected options (only present if action is "submit")
explainOptionNoThe option for which explanation was requested (only present if action is "request_explanation")
explainMessageNoA pre-formatted message asking for explanation (only present if action is "request_explanation")
Behavior4/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 the popup interaction ('opens a popup in the user's browser and waits for their selections'), the 'Other' option behavior, and the return value ('Returns an array of selected options, or indicates if the user skipped'). This is adequate, though it could explain the skip signal in more detail.

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 description is well-structured with clear sections (WHEN TO USE, EXAMPLES, CRITICAL, PARAMETERS) and front-loaded with the core purpose. The warning about parameter separation with wrong/correct examples is valuable but slightly verbose. Overall, each section earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers behavior, usage contexts, and return values, but it fails to align with the actual schema by listing parameters that don't exist (min_selections, max_selections). This mismatch creates a completeness gap. Core interaction is explained, but the inaccuracies prevent a higher score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. However, the description introduces parameters 'min_selections' and 'max_selections' that do not exist in the input schema, potentially misleading the agent. The description largely restates schema fields (label, description, recommended) and the 'CRITICAL' warning, while adding no genuinely useful parameter semantics beyond schema. The presence of non-existent parameters lowers the score.

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's verb and resource: 'Ask the user to choose ONE OR MORE options from a list.' It explicitly distinguishes from sibling tool 'ask_user' by emphasizing multiple selections ('whenever the user can select multiple items'). Examples reinforce the purpose without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a dedicated 'WHEN TO USE THIS TOOL' section with specific scenarios and examples ('Which features do you want?', 'Select the files to include'). It clearly implies single-selection cases are not for this tool, but it does not explicitly name the sibling tool or state exclusions, so it stops short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jens-duttke/mcp-popup-ui'

If you have feedback or need assistance with the MCP directory API, please join our Discord server