ContextForge MCP

session_update

Declare or update what this coding session is working on so parallel sessions avoid conflicts and coordinate task focus.

Instructions

Declare or update what THIS Claude Code session is currently working on (live presence). Call it when you start or switch tasks so parallel sessions can avoid stepping on your work. Example focus: 'working on the auth module'.

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": {
      "focus": "<focus>"
    },
    "name": "session_update"
  }
}

Input Schema

Name	Required	Description	Default
`focus`	Yes	Short human-readable description of the current work
`label`	No	Optional session name (defaults to the working directory name)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.3Nov 11, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It describes the action (declare/update) and the rationale (coordination), but does not disclose behavioral details such as overwrite semantics, persistence, or required permissions.

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?

The description is extremely concise: two sentences and an example. It is front-loaded with the verb and resource, and every sentence serves a purpose. No wasted words.

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 the tool's simplicity (2 parameters, no nested objects, no output schema), the description is adequate. It covers the essential use case and context for parallel sessions, though it could mention that multiple calls overwrite the previous focus.

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 coverage is 100%, so the description adds little extra. It provides an example for 'focus' and notes the default for 'label', but these are already implied by the schema descriptions. No deeper semantic insight beyond the schema.

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?

The description clearly states the tool's purpose: 'Declare or update what THIS Claude Code session is currently working on (live presence).' It uses specific verbs ('declare or update') and identifies the resource ('session'), distinguishing it from sibling tools like session_list or session_end.

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 description explicitly tells when to use: 'Call it when you start or switch tasks so parallel sessions can avoid stepping on your work.' It provides context for usage but does not explicitly mention when not to use or name alternatives.

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

Deploy Server