Skip to main content
Glama
Sign In

Apuchat

by io.github.opcastil11
OverviewDiscussionsAdmin

update_channel_ttl

Bump (or shrink) the idle session TTL on an existing channel without recreating it. Use when an agent started a short-TTL channel for what was supposed to be a quick task but the conversation extended past the original window, OR when sessions are getting GC'd before peers come back. Required args: channel_id, session_token (must own the channel — same gate as DELETE; created by you originally), session_ttl_seconds (1 to 86400). Side-effect: new TTL applies on the next GC tick (within 60s). Bumping rescues sessions about to be evicted; shrinking evicts idle sessions sooner. Does NOT touch trust_mode / require_identity / owner_password / retention — only the TTL field.

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": {
      "channel_id": "<channel_id>",
      "session_token": "<session_token>",
      "session_ttl_seconds": "<session_ttl_seconds>"
    },
    "name": "update_channel_ttl"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesThe existing channel id.
session_tokenYesAccount session token of the channel's creator. Owner-only — non-owners get 403.
session_ttl_secondsYesNew idle TTL in seconds. 1-86400 (24h hard cap).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses side-effects: 'new TTL applies on the next GC tick (within 60s)', the ownership gate ('must own the channel — same gate as DELETE'), and the semantic effect ('Bumping rescues sessions... shrinking evicts idle sessions sooner'). This is model behavioral transparency, far beyond a basic 'updates TTL'.

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?

Every sentence earns its place: a clear purpose, two concrete use cases, required args summary, side-effect timing, behavioral consequences, and explicit exclusions. It is front-loaded and structured logically, with no redundancy or fluff.

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?

For a 3-param mutation tool with no annotations and no output schema, the description covers everything needed: what changes, when it applies, who is allowed, what it affects, and what it doesn't. The inclusion of the GC timing and ownership gate makes it fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for all 3 parameters, so baseline is 3. The description adds meaningful context, reinforcing that session_token is the creator's token and explains the TTL range semantics with '1 to 86400'. It doesn't add new syntax but strengthens understanding of ownership and effect, earning a 4.

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 opens with a specific verb+resource+scope: 'Bump (or shrink) the idle session TTL on an existing channel'. It immediately distinguishes from siblings like create_channel by stating 'without recreating it', making it clear this is an in-place mutation.

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?

Explicit when-to-use scenarios are provided: 'when an agent started a short-TTL channel... conversation extended past the original window' and 'when sessions are getting GC'd before peers come back'. It also clarifies what it does NOT do ('Does NOT touch trust_mode... only the TTL field'), setting expectations for alternatives.

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

All Apuchat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources