Skip to main content
Glama

body_workflow_start

Open an execution ledger for a goal to record observations, decisions, actions, and verification as evidence. Use it to build reports from recorded steps instead of memory.

Instructions

Open an execution ledger for one goal: EYES -> BRAIN -> HANDS -> VERIFY.

Record every step with body_workflow_note(): what you SAW (observation), what you DECIDED and why (decision), what the body DID (action), what PROVED it worked (verification). The ledger is what the final report is built from - evidence instead of memory. The decision stays yours; the body only records it.

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": {
      "goal": "<goal>"
    },
    "name": "body_workflow_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose real behavior: it is a ledger/recorder, not a decision-maker ("the decision stays yours; the body only records it"). It omits whether starting a workflow replaces or resets an existing ledger, whether multiple ledgers can be open, and whether any state is destroyed.

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?

Front-loads the action and the pipeline before the recording doctrine, and most sentences add usable instruction. The EYES/BRAIN/HANDS metaphor adds some length, but the SAW/DECIDED/DID/PROVED mapping justifies it.

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 one-parameter, no-output-schema tool this covers the lifecycle well (open, note, report). It leaves open the return value and the concurrency/reset semantics of opening a new ledger, which an agent needs before calling it repeatedly.

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?

One parameter (goal) with 0% schema coverage, so the description must compensate. It adds meaning by framing the goal as the single scope the ledger is opened for, but gives no guidance on how specific or formatted the goal string should be.

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?

States a concrete verb and resource: "Open an execution ledger for one goal", plus the EYES->BRAIN->HANDS->VERIFY frame that separates it from generic start tools. It logically ties to body_workflow_note and the final report, though it doesn't explicitly contrast with body_task_start or body_role_start.

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?

Gives clear in-context usage: open the ledger first, then record every step via body_workflow_note(), and the ledger feeds the final report. It implies when to use it but never states exclusions, e.g. when to prefer body_task_start or body_role_start instead.

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