BuildBatch

Questions for a BuildBatch room plan

ask_questions

Read-onlyIdempotent

Returns BuildBatch's full ordered question script (about 24 KB) for a detailed room plan: each question for the person, its allowed answers, which are required and when each applies. Takes no arguments.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`v`	No	The version of the script's format.
`ok`	No	false only when the call was refused.
`api`	No	"buildbatch-assistant".
`plan`	No	How to turn the answers into a plan_room call or a /plan.json query.
`error`	No	When ok is false: why.
`title`	No	What the script is for.
`document`	No	"question-script".
`questions`	No	Each question in order, with its allowed answers, whether it is required and when it applies.
`conditions`	No	How to read each question's when and requiredWhen.
`instructions`	No	Its purpose, rules and what to do after the call.
`typicalRooms`	No	The typical rooms, for a person who has not measured.
`specification`	No	The OpenAPI description.
`productFigures`	No	Questions about a product's own figures (a paint's coverage, a pack's size), and the arguments each fills.
`typicalHeightMm`	No	The typical ceiling height, in millimetres.
`typicalOpenings`	No	The typical door and window sizes, by name.
`humanExplanation`	No	A page that explains it to a person.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "api": {
+      "description": "\"buildbatch-assistant\".",
+      "type": "string"
+    },
+    "conditions": {
+      "description": "How to read each question's when and requiredWhen.",
+      "type": "string"
+    },
+    "document": {
+      "description": "\"question-script\".",
+      "type": "string"
+    },
+    "error": {
+      "description": "When ok is false: why.",
+      "type": "string"
+    },
+    "humanExplanation": {
+      "description": "A page that explains it to a person.",
+      "type": "string"
+    },
+    "instructions": {
+      "description": "Its purpose, rules and what to do after the call.",
+      "type": "object"
+    },
+    "ok": {
+      "description": "false only when the call was refused.",
+      "type": "boolean"
+    },
+    "plan": {
+      "description": "How to turn the answers into a plan_room call or a /plan.json query.",
+      "type": "object"
+    },
+    "productFigures": {
+      "description": "Questions about a product's own figures (a paint's coverage, a pack's size), and the arguments each fills.",
+      "type": "array"
+    },
+    "questions": {
+      "description": "Each question in order, with its allowed answers, whether it is required and when it applies.",
+      "items": {
+        "properties": {
+          "ask": {
+            "type": "string"
+          },
+          "choices": {
+            "type": "array"
+          },
+          "fills": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "ifUnknown": {
+            "type": "string"
+          },
+          "notes": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "required": {
+            "type": "boolean"
+          },
+          "type": {
+            "type": "string"
+          },
+          "whenText": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "ask"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "specification": {
+      "description": "The OpenAPI description.",
+      "type": "string"
+    },
+    "title": {
+      "description": "What the script is for.",
+      "type": "string"
+    },
+    "typicalHeightMm": {
+      "description": "The typical ceiling height, in millimetres.",
+      "type": "number"
+    },
+    "typicalOpenings": {
+      "description": "The typical door and window sizes, by name.",
+      "type": "array"
+    },
+    "typicalRooms": {
+      "description": "The typical rooms, for a person who has not measured.",
+      "type": "array"
+    },
+    "v": {
+      "description": "The version of the script's format.",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new operational context: the payload is roughly 24 KB, which matters for context budgeting, and it is a static ordered script rather than a computed result.

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?

Two sentences, front-loaded with the verb and payload size, then a compact enumeration of what the script contains. No filler and nothing that could be cut.

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?

An output schema exists, so return values need not be explained, yet the description still characterizes the payload shape and its fixed size. The only gap is guidance on how this tool relates to the other three BuildBatch tools in a workflow.

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?

There are zero parameters, so the baseline is 4. The description confirms this explicitly with 'Takes no arguments', which matches the empty schema and reinforces rather than merely repeats it.

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?

States a specific verb ('Returns') and resource ('full ordered question script'), plus the payload's internal structure (question text, allowed answers, required flags, applicability conditions). It is clearly distinguishable from plan_room in practice, but it never names a sibling to route the agent explicitly.

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

Usage Guidelines3/5

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

'Takes no arguments' and the description of the returned script imply this is the retrieval step that precedes answering questions, but no when-to-use or when-not-to-use condition is stated, and no alternative (e.g. find_guide or plan_room) is mentioned as a predecessor or substitute.

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

All BuildBatch 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?