Skip to main content
Glama
Sign In
openport

openport

by theodorexli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

finish_session

Saves a final handoff note and closes your work session, ensuring context is preserved for the next agent. Use it when finishing work, and update_context for interim checkpoints.

Instructions

Save a final handoff and close this work session. REQUIRED when finishing work; use update_context for checkpoints while continuing.

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": {
      "session_note": "<session_note>"
    },
    "name": "finish_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNosession_id returned by start_session. If missing/expired, call start_session and follow next_action before retrying.
session_noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.1/5.0
Behavior3/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 clearly states that the tool closes the session and saves a final handoff, but it does not explain irreversibility, what closure entails, or any side effects beyond ending the session.

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?

Two short sentences with no waste. The essential action and the key usage rule are both front-loaded.

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 session-finalization tool with no annotations and no output schema, the description covers the core action and usage condition. It still leaves gaps around what closing means operationally and what the agent should put in the final handoff.

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?

One parameter, session_id, is well described in the schema; the other, session_note, is undocumented in the schema. The description's phrase 'final handoff' implies what session_note should contain, but it does not add concrete guidance about format or expectations.

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 names a specific verb and resource: save a final handoff and close the work session. It also distinguishes this tool from update_context, which is for checkpoints while continuing.

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?

It explicitly says this tool is REQUIRED when finishing work and names update_context as the alternative for continuing work. That gives a clear when-to-use and when-to-use-something-else rule.

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