okto-nexus

Overview Schema Source Related Servers Discussions Admin

inbox_extend

Renew the lease on in-flight messages you have pulled but not finished. All IDs must be in-flight; otherwise nothing is extended.

Instructions

Renew the lease on in-flight messages you pulled but have not finished (now + extend_seconds). All-or-nothing: if any id is not in-flight the call fails per-message and nothing is extended.

Input Schema

TableJSON Schema

Name	Required	Description
`agent_id`	Yes	Your agent_id - the GLOBAL inbox to read (a direct message reaches you in any workspace). REQUIRED.
`session_id`	No	Your session_id from session_open (optional in trust_mode=open; REQUIRED together with session_secret in trust_mode=strict).
`message_ids`	Yes	The message_id(s) whose lease to renew - id or list. REQUIRED. All must be in-flight; otherwise the call fails per-message and nothing is extended.
`extend_seconds`	Yes	New lease duration in seconds, counted from now (REQUIRED; clamped to 10..3600).
`session_secret`	No	session_secret from session_open for session_id (optional in open mode but VALIDATED if supplied; REQUIRED in strict mode).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.10Sep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses the key atomicity trait: all-or-nothing, with per-message failure and no extensions if any id is not in-flight. It also clarifies the lease is extended from now. It does not discuss authentication or return values, but the output schema handles returns and the input schema documents session/trust requirements.

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 focused sentences with no filler. The core action is front-loaded, followed by the critical failure condition. Every sentence earns its place.

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 5-parameter mutation-like tool with 100% schema coverage, an output schema, and no annotations, the description covers the essential behavior: lease renewal and all-or-nothing failure. It does not mention trust-mode auth requirements, but those are fully documented in the schema, so the description is largely complete for correct invocation.

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%, so the schema already explains all parameters, including extend_seconds clamping and session trust modes. The description adds only mild context via '(now + extend_seconds)' and the all-must-be-in-flight constraint, which is also in the schema. Baseline 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?

The description states a specific verb and resource: renew the lease on in-flight messages. It also distinguishes this from ack/finish behavior by specifying messages 'you pulled but have not finished.' An agent can clearly identify the operation without opening the schema.

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 gives clear context for use: messages that are in-flight but not yet finished need their lease renewed. It does not explicitly name alternatives like inbox_ack or state when not to use this tool, so it falls short of full when/when-not guidance, but the implied usage is clear.

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