Body-MCP

reflex_interview

Ask users several questions at once to gather requirements and answers before building, clarifying budget, category, must-haves, and issues with prior tools.

Instructions

Ask the user several questions at once and get the answers back.

Use it before building anything: budget, category, what went wrong with the tools you already tried, light vs heavy, must-haves, must-nevers. With no questions given, the standard Body-MCP set is used.

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": "reflex_interview"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No
`questions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two useful behavioral facts: the call is interactive (asks the user and returns answers) and an omitted questions list falls back to 'the standard Body-MCP set.' It says nothing about blocking behavior, timeouts, or what happens if the user declines or answers partially.

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?

Three short sentences, front-loaded with the core action, then the usage condition, then the default behavior. The topic list is compact and each item adds information about what kinds of questions to batch.

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?

For an interactive, annotation-free tool with no output schema, the definition covers invocation but not return shape: it doesn't say how answers are keyed to the questions asked, or how the standard default set is returned. Adequate to call it, incomplete for predicting its result.

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 0% for two parameters, so the description must compensate. It explains the semantics of 'questions' well, including the null/default fallback, but the 'title' parameter is never mentioned and its purpose is left entirely opaque.

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 opens with a specific verb and resource: 'Ask the user several questions at once and get the answers back.' The phrase 'several questions at once' implicitly distinguishes it from a single-question sibling like reflex_ask, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

It gives clear when-to-use guidance: 'Use it before building anything', followed by a concrete list of topics to cover (budget, category, prior tool failures, light vs heavy, must-haves, must-nevers). There are no exclusions or named alternatives, so it stops short of full alternative routing.

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

Deploy Server