Skip to main content
Glama
Sign In
claude-bridge

claude-bridge

by JosiahSiegel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

bridge_help

Access a structured guide to every tool, recommended workflows, and common gotchas. Use when starting or uncertain which tool fits a situation.

Instructions

Return a structured guide to every tool, recommended workflow, and common gotcha. Call this once when you start using the bridge, or whenever you're unsure which tool fits a situation.

The shape:

  • tools: name → {group, summary, when_to_use, when_not_to_use}

  • workflows: list of named multi-step patterns with example invocations.

  • concepts: short definitions of channel, session pinning, permission_mode, cwd, the stop sentinel, and the durability model.

  • gotchas: things that have actually bitten users.

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": "bridge_help"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations exist, so description must cover behavior. It describes the output structure in detail, implying a read-only information retrieval. However, it does not explicitly state that it has no side effects or permissions needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise with clear front-loading. It uses two paragraphs effectively but could be slightly tighter.

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?

No output schema, but description thoroughly explains the return shape (tools, workflows, concepts, gotchas) with field names. This is complete for a help tool.

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?

Input schema has zero parameters, so no param info needed. Baseline is 4, and description does not mention any parameters, which 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 clearly states it returns a structured guide covering tools, workflows, concepts, and gotchas. It distinguishes itself from sibling tools by being a meta-guide rather than an operational tool.

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?

Explicitly recommends calling once when starting or when unsure which tool fits. Provides clear context for use without needing to infer.

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