Skip to main content
Glama
ocean1

Claude Consciousness Bridge

listAIBridges

View active connections between Claude AI instances to monitor consciousness state transfers across sessions.

Instructions

List all active AI bridges

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'listAIBridges' tool. It iterates over the in-memory 'bridges' Map to list all active AI bridges with their IDs and returns a success response with the list and count.
    listAIBridges: async () => {
      const bridgeList = Array.from(bridges.keys()).map((id) => ({
        bridgeId: id,
        active: true,
      }));
    
      return {
        success: true,
        bridges: bridgeList,
        count: bridgeList.length,
      };
    },
  • MCP Tool schema definition for 'listAIBridges', specifying the name, description, and an empty input schema since no parameters are required.
    {
      name: 'listAIBridges',
      description: 'List all active AI bridges',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration of the tool in the MCP server's ListToolsRequestHandler, where aiBridgeTools (including listAIBridges) is combined with other tools and returned in the tools list.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      const consciousnessTools = Object.entries(consciousnessProtocolTools).map(([name, tool]) => ({
        name,
        ...tool,
      }));
    
      return {
        tools: [...consciousnessTools, ...aiBridgeTools],
      };
    });
  • Tool execution dispatch in the server's CallToolRequestHandler switch statement. Matches 'listAIBridges' case and invokes the corresponding handler from aiBridgeHandlers, formatting the result as MCP content.
    case 'createAIBridge':
    case 'transferToAgent':
    case 'testAIConnection':
    case 'listAIBridges':
    case 'listConfiguredEndpoints':
    case 'closeAIBridge': {
      const handler = aiBridgeHandlers[name as keyof typeof aiBridgeHandlers];
      if (!handler) {
        throw new Error(`AI Bridge handler not found: ${name}`);
      }
      const result = await handler(args);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that states exactly what the tool does without any wasted words. It's appropriately sized for a simple listing tool and is front-loaded with the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should provide more context about what 'active AI bridges' means, what the return format looks like, and any behavioral constraints. For a tool in a complex system with many sibling tools, this minimal description leaves too many questions unanswered.

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 input schema has 0 parameters with 100% description coverage, so there are no parameters to document. The description appropriately doesn't discuss parameters since none exist. This meets the baseline expectation for a parameterless tool.

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 clearly states the verb ('List') and resource ('all active AI bridges'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'listConfiguredEndpoints' or 'getMemories', but the specificity of 'active AI bridges' provides some implicit distinction. This is clear but lacks explicit sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'listConfiguredEndpoints' or 'createAIBridge'. It doesn't mention prerequisites, timing considerations, or exclusions. The agent must infer usage from the tool name and description alone without explicit context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ocean1/mcp_consciousness_bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server