StackFast FractWin Expert Brain

GrowthOS Business Brain Interview

growthos_business_brain_interview

Read-onlyIdempotent

Start or append a GrowthOS Business Brain Interview using the existing interview/session model. Outputs remain draft_review_required before automation.

Input Schema

TableJSON Schema

Name	Required	Default
`action`	No	start
`source`	No
`answers`	No
`company`	No
`lead_id`	No
`tenant_id`	No
`session_id`	No
`customer_name`	No
`customer_email`	No
`interview_type`	No
`audit_project_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	Yes
`public_name`	No
`no_autonomous_outbound`	No
`review_required_before_send`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedJun 11, 2026

removedOutput schema / description

Removed value: -"Structured JSON result envelope. Tool-specific fields vary by product surface; outputs are governed, audit-safe, and omit secrets."

addedOutput schema / properties

Added value: +{
+  "no_autonomous_outbound": {
+    "type": "boolean"
+  },
+  "ok": {
+    "type": "boolean"
+  },
+  "public_name": {
+    "type": "string"
+  },
+  "review_required_before_send": {
+    "type": "boolean"
+  },
+  "tool": {
+    "type": "string"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "ok",
+  "tool"
+]
```

AddedJun 9, 2026

TDQS

C2.6/5.0

Behavior1/5

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

The description directly contradicts the annotations: readOnlyHint is true, yet "start or append" implies modifying interview/session state. This is an annotation contradiction. The added note about draft_review_required is useful but cannot compensate for the conflicting state-change semantics.

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?

The description is a single front-loaded sentence that immediately states the action and resource. It is concise and contains no filler or redundancy.

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 multi-action tool with 11 parameters and contradictory annotations, a one-sentence description is insufficient. It omits parameter semantics, when to use the tool, and fails to clarify behavior beyond the draft_review_required note. The presence of an output schema mitigates but does not eliminate these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 11 parameters and 0% schema description coverage, the description needed to compensate but only provides weak semantic hints like "interview/session model" and "start or append," which loosely map to session_id and the action enum. Most parameters, including answers, company, lead_id, and tenant_id, remain unexplained.

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?

Description clearly states a specific verb and resource: "Start or append a GrowthOS Business Brain Interview." It does not explicitly differentiate from siblings, but the name and action verbs make the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as growthos_scorecard or other interview-related tools. The description does not state prerequisites, exclusions, or selection conditions.

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

All StackFast FractWin Expert Brain 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?