Skip to main content
Glama

Start Session

start_session

Starts a development session by loading project state, PRD, active tasks, and latest handoff to generate a detailed Session Brief for the AI.

Instructions

Start a development session. Loads state, PRD, active tasks, and latest handoff to generate a detailed Session Brief for the AI.

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": "start_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses what gets read and what gets generated (a Session Brief), but it never says whether starting a session mutates or persists any state, whether an existing session is replaced, or whether it fails when no PRD/handoff exists.

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?

Two tight sentences with the action front-loaded and the loaded resources following immediately. Nothing is redundant, though the second sentence packs four loaded artifacts into one clause without grouping or priority.

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?

An output schema exists, so the return value (Session Brief) need not be explained in prose. The description covers inputs read and output produced for a low-complexity, single-optional-parameter tool; the remaining gap is the unexplained `path` argument and the absence of any failure-mode hint.

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 0% for the single `path` parameter, and the description does not mention it at all. An agent must guess that `path` is the project directory being loaded; the default of "." and additionalProperties:false soften the risk, so this is a gap rather than a failure.

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?

The description states a specific verb and resource ("Start a development session") and enumerates what it loads: state, PRD, active tasks, and latest handoff, plus the artifact it produces (Session Brief). This clearly distinguishes it from siblings like get_prd or get_last_handoff, though it never explicitly says it is the bundled alternative to calling those individually.

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?

Usage is implied by the name and the phrase "Start a development session" — an agent can infer it belongs at the beginning of work. However, there is no explicit when-to-use statement, no mention of when to prefer get_context/get_prd/get_last_handoff directly, and no stated prerequisites such as whether a project context must already exist.

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