Elicitly Pro

Ask a human to choose options

elicit_selection

Ask a human to choose one or more options from a caller-supplied list (disambiguation, record matching, picking work items). Async like elicit_approval: returns a pending request decided on the hosted review page; the chosen option ids come back via elicit_result as selectedIds. Options render as rows of a table the Liquid templates and css can customize. Defaults to single-select — raise maxSelections for multi-select.

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": {
      "message": "<message>",
      "options": "<options>"
    },
    "name": "elicit_selection"
  }
}

Input Schema

Name	Required	Description
`css`	No	Custom CSS injected on the review page to style the option table.
`labels`	No	Relabel or localize the action buttons (submit, decline). Each label is trimmed, 1-40 characters; unknown keys are rejected. Button placement and styling stay fixed.
`message`	Yes	The instruction shown above the option list — say what the reviewer is choosing and why.
`options`	Yes	The choices (1-500). Each option is an object with a required unique `id` (returned in `selectedIds`) plus any extra keys, which `rowTemplate` / `hoverTemplate` can reference (e.g. {{ option.name }}).
`rowTemplate`	No	LiquidJS template producing the <td> cells of one option row; the option is exposed as `option` (e.g. <td>{{ option.name }}</td><td>{{ option.score }}</td>). Any link must carry target="_blank" — without it the click replaces the option table with the linked page and the reviewer loses the form. Default: a single cell of `option.label`, falling back to `option.id`.
`hoverTemplate`	No	LiquidJS template for a per-option hover/details card; the option is exposed as `option`. Omit for no hover card.
`maxSelections`	No	Most options the reviewer may pick (default 1 = single-select; clamped to the option count).
`minSelections`	No	Fewest options the reviewer must pick to submit (default 1; 0 allows none).
`footerTemplate`	No	LiquidJS template producing the table footer rows (no variables). Omit for no footer.
`headingTemplate`	No	LiquidJS template producing the <th> cells of the table header (no variables). Omit for no header row.
`expiresInSeconds`	No	How long the request stays decidable, in seconds (default 3600, clamped 60-604800 — 1 minute to 7 days).

Output Schema

Name	Required	Description
`status`	Yes	Always `pending` at creation.
`expiresAt`	Yes	When the request stops being decidable (timestamp).
`reviewUrl`	Yes	URL of the hosted review page where a human decides this request.
`elicitationId`	Yes	Unique id of the created request — pass it to elicit_await / elicit_status / elicit_result / elicit_cancel.
`elicitationDelivered`	Yes	True when the request was also pushed to the connected client as a url-mode elicitation; when false, surface `reviewUrl` to the human yourself.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
Changed5 schema fields changedOct 3, 2026
- changedInput schema / properties / css / maxLength
```
Previous value: -20000New value: +32768
```
- changedInput schema / properties / footerTemplate / maxLength
```
Previous value: -20000New value: +32768
```
- changedInput schema / properties / headingTemplate / maxLength
```
Previous value: -20000New value: +32768
```
- changedInput schema / properties / hoverTemplate / maxLength
```
Previous value: -20000New value: +32768
```
- changedInput schema / properties / rowTemplate / maxLength
```
Previous value: -20000New value: +32768
```

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / rowTemplate / description

Previous value: -"LiquidJS template producing the <td> cells of one option row; the option is exposed as `option` (e.g. <td>{{ option.name }}</td><td>{{ option.score }}</td>). Default: a single cell of `option.label`, falling back to `option.id`."New value: +"LiquidJS template producing the <td> cells of one option row; the option is exposed as `option` (e.g. <td>{{ option.name }}</td><td>{{ option.score }}</td>). Any link must carry target=\"_blank\" — without it the click replaces the option table with the linked page and the reviewer loses the form. Default: a single cell of `option.label`, falling back to `option.id`."

Changed14 schema fields changedSep 5, 2026

addedInput schema / properties / css / description

Added value: +"Custom CSS injected on the review page to style the option table."

addedInput schema / properties / expiresInSeconds / description

Added value: +"How long the request stays decidable, in seconds (default 3600, clamped 60-604800 — 1 minute to 7 days)."

addedInput schema / properties / footerTemplate / description

Added value: +"LiquidJS template producing the table footer rows (no variables). Omit for no footer."

addedInput schema / properties / headingTemplate / description

Added value: +"LiquidJS template producing the <th> cells of the table header (no variables). Omit for no header row."

addedInput schema / properties / hoverTemplate / description

Added value: +"LiquidJS template for a per-option hover/details card; the option is exposed as `option`. Omit for no hover card."

addedInput schema / properties / labels / description

Added value: +"Relabel or localize the action buttons (submit, decline). Each label is trimmed, 1-40 characters; unknown keys are rejected. Button placement and styling stay fixed."

addedInput schema / properties / labels / properties / decline / description
```
Added value: +"Replacement label for the decline button."
```
addedInput schema / properties / labels / properties / submit / description
```
Added value: +"Replacement label for the submit button."
```

addedInput schema / properties / maxSelections / description

Added value: +"Most options the reviewer may pick (default 1 = single-select; clamped to the option count)."

addedInput schema / properties / message / description

Added value: +"The instruction shown above the option list — say what the reviewer is choosing and why."

addedInput schema / properties / minSelections / description

Added value: +"Fewest options the reviewer must pick to submit (default 1; 0 allows none)."

addedInput schema / properties / options / description

Added value: +"The choices (1-500). Each option is an object with a required unique `id` (returned in `selectedIds`) plus any extra keys, which `rowTemplate` / `hoverTemplate` can reference (e.g. {{ option.name }})."

addedInput schema / properties / rowTemplate / description

Added value: +"LiquidJS template producing the <td> cells of one option row; the option is exposed as `option` (e.g. <td>{{ option.name }}</td><td>{{ option.score }}</td>). Default: a single cell of `option.label`, falling back to `option.id`."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "elicitationDelivered": {
+      "description": "True when the request was also pushed to the connected client as a url-mode elicitation; when false, surface `reviewUrl` to the human yourself.",
+      "type": "boolean"
+    },
+    "elicitationId": {
+      "description": "Unique id of the created request — pass it to elicit_await / elicit_status / elicit_result / elicit_cancel.",
+      "type": "string"
+    },
+    "expiresAt": {
+      "description": "When the request stops being decidable (timestamp).",
+      "type": "string"
+    },
+    "reviewUrl": {
+      "description": "URL of the hosted review page where a human decides this request.",
+      "type": "string"
+    },
+    "status": {
+      "const": "pending",
+      "description": "Always `pending` at creation.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "elicitationId",
+    "status",
+    "reviewUrl",
+    "expiresAt",
+    "elicitationDelivered"
+  ],
+  "type": "object"
+}

First observedSep 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover only safety/hints (openWorldHint=false, destructiveHint=false, idempotentHint=false), so the description carries the workflow burden and does so well: it discloses the async pending-request model, that the decision happens on the hosted review page, and that selected ids return via elicit_result as `selectedIds`. It does not cover expiry or cancellation behavior, but the core interaction model is explicit.

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 purpose, then the async contract, then rendering/selection semantics, in roughly four dense sentences. Nearly every clause earns its place, though the rendering sentence and the single/multi-select sentence could be compressed into one without loss.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the description still adds the essential lifecycle (where the decision happens, how the result is fetched) plus the default selection mode for an 11-parameter tool with nested objects. Remaining gaps (expiry, behavior on decline) are minor rather than blocking.

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 description coverage is 100%, so the baseline is 3; the description earns extra by clarifying cross-parameter default semantics — single-select by default with `maxSelections` as the switch to multi-select — and by explaining how `css` and Liquid templates shape the option table. Detail on individual template parameters stays in the schema.

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 first sentence gives a specific verb and resource ('ask a human to choose one or more options from a caller-supplied list') plus concrete use cases (disambiguation, record matching, picking work items). It also distinguishes itself from siblings by name, framing the async flow relative to elicit_approval and elicit_result.

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?

Concrete use cases and a clear routing signal to elicit_result for retrieving the answer, plus the async framing that parallels elicit_approval. It stops short of stating when NOT to use it (e.g. vs elicit_confirm or elicit_form), so an agent must infer the boundary from the selection-shaped framing.

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

All Elicitly Pro tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?