Skip to main content
Glama
CLO Atelier

CLO Atelier

by benproj

Stop the CLO bridge

clo_stop_bridge

Stops the CLO bridge script when requested, ending the active connection; other CLO Atelier tools stay unavailable until the user runs the bridge script again.

Instructions

Stop the bridge script inside CLO. The other tools stop working until the user runs the bridge script again, so only call this when the user asks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clo_stop_bridge"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does the most important thing: it discloses the collateral consequence that all other tools stop working until the user re-runs the bridge script. It stops short of saying what the call returns or whether the stop is immediate versus graceful.

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 short sentences, zero waste, and the action is front-loaded before the caution. Each 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?

For a parameterless, annotation-free control tool this covers the essentials: what it does, what breaks afterwards, and the permission-like condition for calling it. The only gap is the absence of any note about the response or bridging state after the call, which is minor given there is no output schema to lean on.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter language is present.

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 names a specific verb and resource ("Stop the bridge script inside CLO") and implicitly distinguishes itself from every other clo_* sibling, which all depend on the bridge staying alive. An agent can tell immediately that this is the shutdown counterpart to the rest of the toolset.

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 an explicit gating condition — "only call this when the user asks" — which functions as a clear when-not rule for all other situations. It does not name an alternative tool (there arguably is none for stopping the bridge), so it falls just short of the full when/when-not/alternatives standard.

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