StackFast FractWin Expert Brain

GrowthOS Revenue Capture Packet

growthos_revenue_capture_packet

Read-onlyIdempotent

Return a GrowthOS revenue-capture packet: scorecard, review-gated contact drafts, CogentCast site-review receipt composition, and summary for supplied local-business evidence. GrowthOS consumes CogentCast receipts instead of recreating website-review logic. No autonomous outbound.

Input Schema

TableJSON Schema

Name	Required	Description
`sender`	No
`prospect`	Yes
`cogentcast_site_review`	No	Optional CogentCast site-review request or precomputed receipt. GrowthOS consumes this receipt instead of recreating website review logic.
`include_cogentcast_site_review`	No	Fetch a CogentCast dry-run site-review receipt for the supplied website_url and compose it into step 3.

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.

Changed2 schema fields changedJun 24, 2026

addedInput schema / properties / cogentcast_site_review

Added value: +{
+  "description": "Optional CogentCast site-review request or precomputed receipt. GrowthOS consumes this receipt instead of recreating website review logic.",
+  "type": "object"
+}

addedInput schema / properties / include_cogentcast_site_review

Added value: +{
+  "description": "Fetch a CogentCast dry-run site-review receipt for the supplied website_url and compose it into step 3.",
+  "type": "boolean"
+}

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful context beyond those annotations: GrowthOS consumes CogentCast receipts rather than recreating website-review logic, and 'No autonomous outbound' clarifies that the tool produces drafts/packets without sending them. There is no contradiction with the annotations.

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 sentences with no filler: the first front-loads the deliverable and its components, the second adds the key integration behavior, and the third states a crucial constraint. Every sentence earns its place.

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 a 4-parameter packet tool, the description covers the deliverable components, the CogentCast integration, and the no-outbound constraint, with output schema and annotations covering return values and safety. Yet it does not explain the required `prospect`/`sender` shapes and gives no explicit guidance for choosing among the many sibling packet tools, so the description is not fully complete for an autonomous agent.

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 descriptions cover the two CogentCast-related parameters, and the main description loosely ties `prospect` to 'supplied local-business evidence.' However, `sender` and `prospect` are nested objects with no property-level schema descriptions, and the description does not meaningfully explain what should go into them, leaving a real gap at 50% coverage.

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 uses a specific verb ('Return') and a specific resource ('GrowthOS revenue-capture packet'), then enumerates the packet's components: scorecard, review-gated contact drafts, CogentCast site-review receipt composition, and summary. This clearly distinguishes it from sibling packet generators even without naming them directly.

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?

The description gives useful context: the tool is for 'supplied local-business evidence' and explicitly states 'No autonomous outbound,' which tells the agent the packet is not to be sent. However, it never names sibling alternatives or states when to prefer this packet over growthos_digital_clone_packet or growthos_opportunity_scout_packet.

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?