Boardroom Bob

run_five_whys

Drill past symptoms to the root cause.

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": {
      "input": "<input>"
    },
    "name": "run_five_whys"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes	Your problem, decision, project, or question to analyze with this framework.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It hints this is an analytical operation rather than a mutation, but discloses nothing about depth of iteration, whether the run is interactive, expected latency, or what the agent receives back from a framework invocation.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the definition's other gaps rather than a virtue of precise packing.

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

Completeness2/5

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

For a framework-runner tool with no output schema and no annotations, the description leaves the agent without knowledge of the return shape, the number of 'whys' produced, or how the output should be consumed. Compared to a tool invoked among 18 similar frameworks, this is under-specified.

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?

There is only one parameter and schema description coverage is 100%, so the schema already explains that 'input' accepts a problem, decision, project, or question. The description adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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

Purpose3/5

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

The description gives a goal-oriented verb ('Drill past symptoms') and an outcome ('to the root cause'), which conveys the intent of root-cause analysis. However, it never names the framework (Five Whys) or its mechanism, and it does not distinguish this from methodologically adjacent siblings like run_first_principles or run_inversion.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool versus the 18 sibling frameworks, no mention of prerequisites, and no exclusions. The agent must infer applicability purely from the metaphor in the sentence.

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

All Boardroom Bob 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?