ChannelTerm

Overview Schema Source Related Servers Discussions Admin

Renew Session Lease

terminal_renew_lease

Renew an exclusive Session lease before it expires to keep terminal access active for the current operation. Provide the active session ID and owner capability.

Instructions

Renew an exclusive Session lease owned by this operation before it expires.

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_id": "<session_id>",
      "owner": "<owner>"
    },
    "name": "terminal_renew_lease"
  }
}

Input Schema

Name	Required	Description	Default
`owner`	Yes	Opaque caller-generated lease owner capability.
`session_id`	Yes	Active Session ID or short reference.

Output Schema

Name	Required	Description	Default
`type`	Yes
`state`	Yes
`created_at`	Yes
`expires_at`	Yes
`session_id`	Yes
`transfer_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.2Oct 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the lease is exclusive and owner-scoped, but omits the operationally important behavior: how much the TTL is extended, what happens on a failed/expired renewal, and that repeated calls stack extensions (implied by idempotentHint=false).

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?

A single front-loaded sentence with no filler; the critical timing constraint sits at the end of a compact statement rather than buried in prose.

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?

An output schema exists, so return values need no explanation, and parameters are fully covered. However, for a non-idempotent lease mutation the description never states the consequence of missing the expiry window or whether ownership is lost, which is the main thing an agent needs to decide when to call it.

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% and both parameters are documented in-schema, so the baseline of 3 applies. The description's 'owned by this operation' loosely ties to the owner capability, but no format, matching rules, or mismatch behavior is added beyond the schema.

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?

Specific verb (Renew) plus specific resource (an exclusive Session lease owned by this operation), with a timing qualifier ('before it expires'). The verb alone cleanly separates it from terminal_acquire_lease and terminal_release_lease, though those siblings are never named explicitly.

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?

'before it expires' hints at when to call, but there is no guidance on cadence, on what to do if the lease has already lapsed, or on why one would renew rather than re-acquire via terminal_acquire_lease. Usage is implied rather than stated.

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

Deploy Server