Skip to main content
Glama

Synthesize JIT Session Orientation

nomos_handshake
Read-onlyIdempotent

Discover a repository's active worktree, current task phase, and next allowed actions at agent startup, without changing files or Git hooks.

Instructions

Synthesize read-only Just-In-Time (JIT) session orientation, active task phase, and Next Actions for a repository without modifying files or Git hooks. Use when starting an agent turn to discover the active worktree and allowed phase actions. Do NOT use when checking global daemon/DB health without JIT directives (use nomos_status instead) or listing backlog tasks (use nomos_task_dag instead).

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

Input Schema

NameRequiredDescriptionDefault
dirNoTarget repository root or subdirectory path (defaults to current working directory)..

Output Schema

NameRequiredDescriptionDefault
phaseNoActive Nomos lifecycle phase.
next_actionsNoDeterministic phase affordances.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is largely covered. The description reinforces this with concrete scope ('without modifying files or Git hooks') and names the three artifacts returned, which goes slightly beyond the annotations by clarifying what 'orientation' actually contains.

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 front-loaded sentences — purpose, when-to-use, when-not-to-use — with no filler or redundant restatement of the name. The negative guidance is placed after the positive guidance, matching reading order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the tool is low-complexity with one optional parameter. The description covers purpose, invocation timing, alternatives, and mutation-free behavior — everything an agent needs before calling.

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?

The single optional 'dir' parameter already has full schema coverage with a description, default, and examples. The description adds no path semantics (e.g., whether subdirectories inherit the parent worktree), so the schema does all the work and baseline 3 applies.

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 ('Synthesize') and concrete outputs ('JIT session orientation, active task phase, and Next Actions') scoped to a repository, with an explicit non-mutation qualifier. It is clearly distinguishable from nomos_status (daemon/DB health) and nomos_task_dag (backlog listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use when starting an agent turn to discover the active worktree and allowed phase actions') plus two explicit exclusions that route to named siblings. The agent knows both when to call it and which tool to pick otherwise.

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