Skip to main content
Glama

Choose

choose

Presents clickable option cards so users pick between discrete alternatives instead of typing a reply. Call it to capture a decision, then wait for the "I selected:" message before continuing.

Instructions

Present the user with a set of options to choose from.

Call this tool when you need the user to make a decision between discrete alternatives. Use it proactively — don't ask the user to type their choice in chat when you can present clean, clickable options instead.

The user will see a card with one button per option. When they click one, their choice appears as a message in the conversation (as if the user typed it), like:

"Which deployment strategy?" — I selected: Blue-green

IMPORTANT: After calling this tool, you MUST stop and wait for the user's response. Do not continue or take any other actions until you see the "I selected:" message.

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": {
      "prompt": "<prompt>",
      "options": "<options>"
    },
    "name": "choose"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional heading for the card.
promptYesThe question or decision to present to the user.
optionsYesList of options the user can choose from.

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 of behavioral transparency. It thoroughly discloses the user experience (a card with buttons), the result format ('I selected:'), and explicitly states that the tool blocks further agent actions until the user responds: 'After calling this tool, you MUST stop and wait for the user's response.' This is a critical behavioral trait disclosed clearly.

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 well-structured and front-loaded. It opens with the core purpose, then moves to usage context, then details the user interaction and the blocking requirement. Every sentence adds value, and the length is appropriate—comprehensive without being verbose.

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?

The tool has no output schema, but the description compensates by explaining the result flow (the user's choice appears as a message). It covers the full interaction lifecycle, including the critical post-call waiting behavior. For a tool with 3 simple parameters and no complex nesting, this description is fully complete.

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 coverage is 100%, so each parameter already has a description. The tool description adds contextual nuance (e.g., options become clickable buttons) but does not significantly extend the parameter semantics beyond what the schema provides. The example of the prompt format is helpful but minor. Baseline 3 is appropriate given the schema's completeness.

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 explicitly states the tool's function: 'Present the user with a set of options to choose from.' This is a specific verb-resource pair. The sibling tools are all GitHub-focused (e.g., github_get_project_fields, github_create_issue), so this tool is clearly distinct in purpose, eliminating any ambiguity about when to call it.

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?

The description gives explicit when-to-use guidance: 'Call this tool when you need the user to make a decision between discrete alternatives.' It also advises proactive use and warns against having the user type a choice in chat. This directly addresses the decision between this tool and an alternative (chat-based input), with clear instructions.

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