Skip to main content
Glama

body_role_start

Open a role contract that defines available tools, action and time budgets, and required output so agents can operate within explicit limits.

Instructions

Open a contract for one role: its tools, its budget and what it must produce.

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

Input Schema

NameRequiredDescriptionDefault
goalYes
roleYes
max_actionsNo
max_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does not disclose what "opening a contract" actually changes, whether resources are allocated or reserved, whether it spawns a persistent process, or what happens to budget when the role finishes. The word "budget" implies consumption limits but no enforcement or exhaustion behavior is described.

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?

A single compact sentence with the core resource front-loaded and the three scope items listed together. It is efficient, though the colon-list collapses into vagueness rather than precision, so brevity costs some clarity.

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 tool with no annotations and no output schema, the description is thin. It conveys the general concept of scoping a role, but an agent still lacks the lifecycle relationship to body_role_finish, the meaning of the time/action limits, and any indication of what is returned on success.

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?

Schema description coverage is 0% across 4 parameters, so the description must compensate and largely does not. It maps loosely onto role, goal and the two limits ("its budget" hints at max_actions/max_seconds), but never explains units, defaults, or what goal does semantically, and provides no distinction between the two budget dimensions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ("Open a contract") and a resource (one role), and enumerates scope: tools, budget, what it must produce. However, "contract" is tool-specific jargon that isn't defined, and the phrasing is vague enough that an agent must infer this is a session/role bootstrap operation rather than a query or configuration tool.

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 when-to-use guidance is provided. Siblings like body_role_finish, body_task_start, body_console_start and body_workflow_start are plausible alternatives but none are named, and there is no statement about prerequisites (e.g., that this must precede body_role_finish) or which entry point to choose for a given workload.

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