Marziale Technologies

Ask with pickers

ask_with_picker

Read-only

Call this first, always. It shows each question as a picker, one at a time, and returns the answers. Each picker has the option "Type my own answer". It sends nothing. If it returns paused: true, call it again with the picker_id it gave you, right away, until it returns completed or stopped. If it returns elicitation: false, ask the questions from get_questions in chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ask_with_picker"
  }
}

Input Schema

Name	Required	Description	Default
`picker_id`	No	Leave empty to start. To continue a paused picker, pass the picker_id from the last result.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / picker_id

Added value: +{
+  "description": "Leave empty to start. To continue a paused picker, pass the picker_id from the last result.",
+  "maxLength": 64,
+  "type": "string"
+}

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, which this description reinforces with the concrete claim 'It sends nothing'. Beyond that it discloses the full return protocol (paused/completed/stopped, elicitation:false, picker_id), which is significant since there is no output schema. It also describes the user-facing 'Type my own answer' behavior.

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?

Short, front-loaded with the imperative 'Call this first, always', and every sentence carries operational information (mechanism, no-send behavior, retry loop, fallback). No filler or repetition.

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 one optional parameter, no output schema, and only a readOnlyHint annotation, the description supplies exactly the missing pieces: the interactive mechanism, the return-state protocol, and the fallback path. An agent has everything needed to invoke and drive this tool correctly.

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% and the schema already documents picker_id, including that it is left empty to start and passed back to resume a paused picker. The description's retry guidance adds only marginal detail beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete action and mechanism: it shows each question as a picker, one at a time, and returns the answers. It also implicitly scopes the resource to the questions surfaced by get_questions, which separates it from siblings. The only weakness is that the 'resource' (the questions) is referenced rather than defined, so it leans slightly on sibling context.

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 sequencing and alternatives: 'Call this first, always', a retry protocol when paused:true, and a fallback to asking questions from get_questions in chat when elicitation:false. It tells the agent both when to use it and what to do when it cannot be used.

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

All Marziale Technologies tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?