BuildBatch

Find a BuildBatch guide

find_guide

Read-onlyIdempotent

Finds BuildBatch's guides for a decorating or flooring question (how long between coats, how many tiles in a square metre, what to buy to lay laminate), and returns up to three with each guide's own short answers and its address. It does not work out quantities for a room.

Input Schema

Name	Required	Description	Default
`query`	Yes	The question, in plain words.

Output Schema

Name	Required	Description
`ok`	Yes	true: the guides were searched (none may match). false: the query was refused.
`api`	No	On a refusal of an argument: "buildbatch-assistant".
`note`	No	Whose answers they are and how far they have been checked, or that no guide matched.
`error`	No	When ok is false: why.
`query`	No	The question as read.
`guides`	No	Up to three guides, best first.
`allGuides`	No	The list of every guide.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "How long between coats of paint?"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "allGuides": {
+      "description": "The list of every guide.",
+      "type": "string"
+    },
+    "api": {
+      "description": "On a refusal of an argument: \"buildbatch-assistant\".",
+      "type": "string"
+    },
+    "error": {
+      "description": "When ok is false: why.",
+      "type": "string"
+    },
+    "guides": {
+      "description": "Up to three guides, best first.",
+      "items": {
+        "properties": {
+          "answers": {
+            "description": "The guide's own short answers, as published.",
+            "items": {
+              "properties": {
+                "answer": {
+                  "type": "string"
+                },
+                "question": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "question",
+                "answer"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "summary": {
+            "description": "What it answers.",
+            "type": "string"
+          },
+          "title": {
+            "description": "The guide's title.",
+            "type": "string"
+          },
+          "url": {
+            "description": "Its address.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "maxItems": 3,
+      "type": "array"
+    },
+    "note": {
+      "description": "Whose answers they are and how far they have been checked, or that no guide matched.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "true: the guides were searched (none may match). false: the query was refused.",
+      "type": "boolean"
+    },
+    "query": {
+      "description": "The question as read.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

AddedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior. The description adds useful return context ('up to three' guides, each with short answers and an address) and a scope limitation, though it does not mention rate limits or authentication.

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?

The purpose and return format are front-loaded, followed by a useful exclusion. The first sentence is dense with parenthetical examples, but every part contributes to understanding the tool.

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?

For a simple one-parameter guide search with an output schema already present, the description covers what the tool does, when to use it, its output shape at a high level, and a key limitation. The only notable omission is explicit sibling routing.

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 coverage is 100%, so the baseline is 3. The description still adds value by giving plain-language question examples and emphasizing that the query is a natural-language question, reinforcing the parameter's intended form.

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 names a specific verb and resource ('Finds BuildBatch's guides') and grounds it with concrete decorating/flooring question examples. It also states the scoping boundary ('does not work out quantities for a room'), so an agent can distinguish it from room-planning siblings.

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 clearly says when to use it: for decorating or flooring questions like drying times, tile counts, or buying materials. It also states when not to use it for quantity calculations, but it does not explicitly name which sibling to use instead.

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?