Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bridge_statusD

Execute bridge status through the v2 service.

bridge_inboxD

Execute bridge inbox through the v2 service.

bridge_sendD

Execute bridge send through the v2 service.

bridge_claimD

Execute bridge claim through the v2 service.

bridge_doneD

Execute bridge done through the v2 service.

bridge_showD

Execute bridge show through the v2 service.

bridge_boardD

Execute bridge board through the v2 service.

bridge_questionD

Execute bridge question through the v2 service.

bridge_answerD

Execute bridge answer through the v2 service.

bridge_reviewD

Execute bridge review through the v2 service.

bridge_wakeD

Execute bridge wake through the v2 service.

bridge_agentsD

Execute bridge agents through the v2 service.

bridge_activityD

Execute bridge activity through the v2 service.

bridge_contextD

Execute bridge context through the v2 service.

bridge_cleanD

Execute bridge clean through the v2 service.

bridge_doctorD

Execute bridge doctor through the v2 service.

bridge_projectD

Execute bridge project through the v2 service.

bridge_whoamiC

Execute bridge whoami through the v2 service.

bridge_who_coordinatesD

Execute bridge who-coordinates through the v2 service.

bridge_logD

Execute bridge log through the v2 service.

bridge_migrateD

Execute bridge migrate through the v2 service.

bridge_exportD

Execute bridge export through the v2 service.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.9/5.0

Scored across 22 tools

Disambiguation2/5

Every tool carries the identical boilerplate description ('Execute bridge_<name> through the v2 service'), so descriptions provide zero help in telling tools apart. Names alone leave several clusters ambiguous: bridge_show/status/board/context/inbox, bridge_export/log/activity, and bridge_clean/doctor/migrate could easily be confused.

Naming Consistency4/5

All 22 tools use a uniform bridge_<snake_case> prefix, which is highly predictable. The only minor deviation is mixing nouns (inbox, board, context, agents) with verbs (send, claim, done) and the multi-word bridge_who_coordinates, but the pattern remains readable.

Tool Count3/5

At 22 tools the surface is heavy for what appears to be an agent-coordination bridge; each tool may earn its place, but the sheer number plus identical descriptions makes the set feel bloated and hard to navigate.

Completeness3/5

The names suggest a fairly full coordination lifecycle (send, inbox, claim, done, question/answer, review, board, activity, log, whoami, migrate, doctor), but with no meaningful descriptions it is impossible to confirm coverage. Obvious update/edit or delete/close operations for messages and tasks are not clearly represented.