ChatGPT2LocalBridge

by Harzva

Overview Schema Source Related Servers Discussions Admin

Local

Restart Bridge Service

service.restart

Destructive

Restart bridge or ngrok service after confirmation to restore local connectivity for ChatGPT operations.

Instructions

Restart one fixed launchd service: bridge or ngrok. Requires confirm=true.

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": {
      "service": "<service>",
      "confirm": "<confirm>"
    },
    "name": "service.restart"
  }
}

Input Schema

Name	Required	Description	Default
`service`	Yes
`confirm`	Yes

Output Schema

Name	Required	Description	Default
`service`	Yes
`label`	Yes
`exitCode`	Yes
`stdout`	Yes
`stderr`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true, and the description adds the mandatory confirm parameter required for execution. This provides behavioral context beyond the annotations, though more detail on what restart entails (e.g., service downtime) is missing.

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 concise sentences front-load the purpose and immediately follow with the critical usage requirement. No filler or redundancy.

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?

The description covers the essential aspects: what services, required confirm flag. Since an output schema exists, return values need not be described. It is complete enough for a simple restart operation.

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?

Despite 0% schema coverage, the description adds meaning to the confirm parameter (must be true) and implies the service parameter's values (bridge, ngrok via enum). It compensates for the lack of schema descriptions.

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 clearly states the action (restart) and resource (launchd service), listing the two specific services (bridge, ngrok). It effectively distinguishes from sibling tools like bridge.health and bridge.logs by focusing on the restart action.

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 explicitly requires confirm=true, which is a critical usage guideline. While it doesn't explicitly contrast with alternatives, the context of siblings (health, logs, etc.) makes it clear when to use this tool.

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