Skip to main content
Glama

body_console_start

Starts a local-only console for monitoring executor activity and canceling or disconnecting tasks; returns a session-tokenized 127.0.0.1 URL.

Instructions

Start the optional local Body Console (activity timeline + cancel/disconnect).

Binds to 127.0.0.1 only and requires a session token; the returned URL contains it. The console shows REAL executor events — tasks, actions, verifications, blockers — and never page content. Stop it with body_console_stop().

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "body_console_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the 127.0.0.1-only binding, the session-token requirement, that the token is embedded in the returned URL, the exact data exposed (executor events, never page content), and the lifecycle endpoint. It does not say what happens if the console is already running or the port is occupied, which matters for a server-starting tool.

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-loaded with the action, then security/scope detail, then teardown — a sensible order with no filler. Sentence fragments in the first line ('activity timeline + cancel/disconnect') are compact rather than noisy, though the 'it' in 'the returned URL contains it' relies on the preceding sentence for resolution.

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 one-optional-param server-start tool with no output schema, the description covers purpose, security posture, data boundary, return URL, and how to shut it down. Remaining gaps are the undocumented port parameter and unstated behavior on port conflict or duplicate start.

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?

The single parameter 'port' (default 8765) has 0% schema description coverage and is never mentioned in the description, even though it materially affects the returned URL. The description discusses a host binding but leaves the one tunable input completely unexplained in both places.

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?

States a specific verb and resource ('Start the optional local Body Console') and parenthetically defines what the console is (activity timeline + cancel/disconnect), so the agent knows it launches a local observability server. It also names its counterpart tool, body_console_stop(), making the pair unambiguous among the many body_* start tools.

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?

The word 'optional' signals this is not required for normal operation, and the closing sentence explicitly routes teardown to body_console_stop(). There is no explicit statement of when an agent should want this console (e.g., debugging/monitoring an executor run), so the usage trigger is implied rather than stated.

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