Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

session_start

Idempotent

Start or resume an agent work session and bind it to this connection. Get a project briefing and automatically scope later memory and note calls to that project.

Instructions

Begin or resume an agent work session and bind it to this connection. Returns the project briefing. Later memory/recall/notes calls inherit this session's project scope, so you rarely pass project again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoAbsolute working directory; auto-mapped to a project from the repo root on a repo's first session (no setup step -- `seamlessd map-repo` only overrides the derived slug)
hostNoMachine this agent runs on (hostname). Defaults to the X-Seamless-Host header, then to the daemon's own host; pass it only when dialling a daemon on another machine
nameNoOptional stable session name; reusing a name resumes that session
modelNoModel id powering this agent, exactly as the provider names it (e.g. claude-fable-5, gpt-5.5). Stamped onto memories/notes this session writes; hooks keep it current for Claude Code/Codex sessions, so pass it mainly from other clients
sourceNowhat began this session (default explicit)
repo_rootNoAbsolute git repository root enclosing cwd, resolved on YOUR machine. Required when host is not the daemon's: the daemon cannot read your filesystem to find it
repo_originNoThe repository's origin remote URL, which is how the same repo checked out on two machines is recognized as one project
main_worktree_rootNoAbsolute root of the repository's MAIN checkout when repo_root is a linked worktree; defaults to repo_root

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.1
    • addedInput schema / properties / host
      Added value: +{
+  "description": "Machine this agent runs on (hostname). Defaults to the X-Seamless-Host header, then to the daemon's own host; pass it only when dialling a daemon on another machine",
+  "type": "string"
+}
    • addedInput schema / properties / main_worktree_root
      Added value: +{
+  "description": "Absolute root of the repository's MAIN checkout when repo_root is a linked worktree; defaults to repo_root",
+  "type": "string"
+}
    • addedInput schema / properties / repo_origin
      Added value: +{
+  "description": "The repository's origin remote URL, which is how the same repo checked out on two machines is recognized as one project",
+  "type": "string"
+}
    • addedInput schema / properties / repo_root
      Added value: +{
+  "description": "Absolute git repository root enclosing cwd, resolved on YOUR machine. Required when host is not the daemon's: the daemon cannot read your filesystem to find it",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.3
    • changedInput schema / properties / source / description
      Previous value: -"what began this session (default startup)"New value: +"what began this session (default explicit)"
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark idempotentHint true and destructiveHint false; the description adds meaningful context: the session binds to the connection, returns the project briefing, and scopes later memory/recall/notes calls. This discloses the side-effectful statefulness beyond the annotation flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with the main action front-loaded and no filler. Each sentence earns its place: what it does, what it returns, and the scope-inheritance consequence.

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?

Given a complex 8-parameter optional schema and no output schema, the description supplies the key behavioral expectations (return value and session scoping). It doesn't detail the project briefing contents, but the rich schema covers parameter semantics, so an agent has enough to invoke it correctly.

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% and the parameter descriptions are already detailed (e.g., when to pass host, repo_root, main_worktree_root). The description adds no parameter-specific meaning, so a baseline of 3 is appropriate.

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?

Description states 'Begin or resume an agent work session and bind it to this connection,' a specific verb and resource, and immediately distinguishes its side effect ('Later memory/recall/notes calls inherit this session's project scope') from sibling tools. It clearly answers what the tool does without restating the name.

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?

It gives clear context on when to call: start a session first so subsequent memory/recall/notes calls inherit project scope, and notes that you 'rarely pass project again.' It does not explicitly name alternatives like session_update or session_end, so the distinction is implicit rather than a formal when/where-not list.

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

Deploy Server

Other Tools