Skip to main content
Glama
Sign In
ChannelTerm

ChannelTerm

by akira-init1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Renew External GDB Bridge

debug_bridge_renew

Renew an external RSP bridge’s management heartbeat and internal lease to keep its session alive, including while listening or disconnected, before grace-period expiry.

Instructions

Renew the external RSP bridge's management heartbeat and internal lease, including while listening or disconnected. Current authenticated rsp-client connections renew automatically. The 60-second grace and 24-hour absolute maximum cannot be resurrected. Expiry closes the serial Session without claiming target restoration.

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": {
      "owner": "<owner>",
      "bridge_id": "<bridge_id>"
    },
    "name": "debug_bridge_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesSecret management capability, 32..128 characters; distinct from the generated TCP connection token.
bridge_idYesOpaque bridge_id returned by debug_bridge_start; not a Session reference.

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key lifecycle behavior: current authenticated connections renew automatically, the 60-second grace and 24-hour absolute maximum cannot be resurrected, and expiry closes the serial Session without claiming target restoration. This adds substantial operational context for a non-read-only, non-idempotent renewal operation.

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 front-loaded with the action and scope, then spends its remaining sentences on automatic renewal, lease limits, and expiry consequences. Every sentence carries relevant information and none is wasted.

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?

With an output schema present, return values need not be explained. The description, annotations, and fully described parameters together cover safety, scope, lifecycle limits, and expiry consequences well enough for an agent to invoke the tool correctly.

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 documents owner as a secret management capability and bridge_id as an opaque ID from debug_bridge_start. The description does not add parameter-specific meaning beyond that baseline.

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?

The description states a specific verb and resource: renewing the external RSP bridge's management heartbeat and internal lease. It clarifies that this applies while listening or disconnected and that current authenticated rsp-client connections renew automatically, but it does not explicitly position the tool against sibling renewal or bridge tools.

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?

It gives clear usage context by implying renewal is for bridges that are listening or disconnected, and it excludes current authenticated rsp-client connections because they renew automatically. It does not name alternative tools or lay out full preconditions, so it stops short of explicit when/when-not/alternatives guidance.

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