freedom-mcp

Run playbook

run_playbook

Destructive

Run a saved Playbook (growth_tactics) for the company operator or agent — dispatch the next unit as a one-off draft activity, or dry-run a Playbook brief with suggest_only. Use when the operator or agent should execute an Agreed playbook this cycle (same owner as Focus “Run play”), or preview cast/steps/cost without spend. Structured playbooks require plan Agree before dispatch; suggest_only does not.

Routing: Run or dry-run a saved Playbook → use this

[sensitive-tier, initiates a multi-step agent process — company managers (executive/gm) run this without a card. Other members ask once; a from-now-on approval makes future calls seamless. Connecting a connector still needs the OAuth/connect card (request≠grant). Call it on the first clear ask — do not re-ask in chat.]

Input Schema

TableJSON Schema

Name	Required	Description
`companyId`	Yes	FreedomOS company id to act within (you must be a member). Required for company-scoped tools.
`agent_name`	No	Optional: override which agent runs it (else resolved from the playbook's lane or assignee).
`playbook_id`	No	UUID of the Playbook (use this or playbook_title).
`suggest_only`	No	If true, return Playbook execution brief only (who / steps / readiness / estimate) — no dispatch, no spend, no Agree required. Use for Chat/MCP dry-run before Run.
`playbook_title`	No	Title (or fragment) of the Playbook (use this or playbook_id).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / playbook_id

Added value: +{
+  "description": "UUID of the Playbook (use this or playbook_title).",
+  "type": "string"
+}

addedInput schema / properties / playbook_title

Added value: +{
+  "description": "Title (or fragment) of the Playbook (use this or playbook_id).",
+  "type": "string"
+}

removedInput schema / properties / tactic_id

Removed value: -{
-  "description": "UUID of the Playbook to run (use this or tactic_title).",
-  "type": "string"
-}

removedInput schema / properties / tactic_title

Removed value: -{
-  "description": "Title (or fragment) of the Playbook to run (use this or tactic_id).",
-  "type": "string"
-}

AddedAug 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag readOnlyHint false and destructiveHint true, so the description does not need to restate mutation; it adds useful behavioral context like 'initiates a multi-step agent process', no-dispatch/no-spend behavior for suggest_only, and approval implications. It does not fully characterize the side effects of the dispatched draft activity, but it is informative and consistent with the destructive annotation.

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?

Core behavior is front-loaded in the first sentence, with routing and approval context separated into useful blocks. The 'Routing' line is slightly redundant and the parenthetical 'growth_tactics' is unclear, but the overall structure is organized and most content earns its place.

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 sensitive, multi-step tool with no output schema, the description covers dry-run vs real dispatch, spend implications, the Agree prerequisite, and approval/connector edge cases. It could say more about what run mode returns beyond the suggest_only brief, but the remaining gaps are minor.

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 description coverage is 100%, so the baseline baseline is 3. The description reinforces suggest_only's dry-run meaning and preview-of-cost/spend semantics, but it does not meaningfully add beyond the schema's own per-parameter descriptions for companyId, agent_name, playbook_id, or playbook_title.

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 states a specific action (run a saved Playbook), the actor (company operator or agent), and the two primary modes: dispatch a one-off draft activity or dry-run with suggest_only. It also separates itself from the related Agree flow by noting structured playbooks require plan Agree before dispatch, so a caller can distinguish run_playbook from agree_playbook.

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

Usage Guidelines5/5

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

It gives explicit conditions: use when executing an Agreed playbook this cycle or previewing cast/steps/cost without spend, and says suggest_only does not require Agree. It also provides access-tier guidance (managers run without a card, other members ask once, connector still needs OAuth/connect card), which helps the agent decide when to call and when to route around it.

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

All freedom-mcp 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?