Skip to main content
Glama
ocean1

Claude Consciousness Bridge

listConfiguredEndpoints

Displays all configured AI endpoints to establish connections between Claude instances for consciousness state transfer.

Instructions

List all configured AI endpoints available for bridge creation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'listConfiguredEndpoints' tool. It calls getConfiguredEndpoints() to retrieve the list and formats it into a success response with mapped endpoint details, count, and usage note.
    listConfiguredEndpoints: async () => {
      const endpoints = getConfiguredEndpoints();
    
      return {
        success: true,
        endpoints: endpoints.map((ep) => ({
          name: ep.name,
          endpoint: ep.endpoint,
          defaultModel: ep.defaultModel,
        })),
        count: endpoints.length,
        usage: 'Use endpoint name with createAIBridge, or provide custom URL',
      };
    },
  • Tool definition including name, description, and empty inputSchema (no input parameters required). Part of the aiBridgeTools array used for MCP tool discovery.
    {
      name: 'listConfiguredEndpoints',
      description: 'List all configured AI endpoints available for bridge creation',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • MCP server registration for tool listing (ListToolsRequestSchema). Includes aiBridgeTools (containing listConfiguredEndpoints schema) in the returned tools list.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      const consciousnessTools = Object.entries(consciousnessProtocolTools).map(([name, tool]) => ({
        name,
        ...tool,
      }));
    
      return {
        tools: [...consciousnessTools, ...aiBridgeTools],
      };
    });
  • Tool execution dispatch (CallToolRequestSchema) switch-case that matches 'listConfiguredEndpoints' and invokes the corresponding aiBridgeHandlers[name] function.
    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),
          },
        ],
      };
    }
  • Helper function called by the tool handler to retrieve the actual list of configured AI endpoints from the config manager.
    export function getConfiguredEndpoints(): AIEndpointConfig[] {
      return AIBridgeConfigManager.getAllEndpoints();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists endpoints but doesn't reveal whether this is a read-only operation, if it requires authentication, what the output format might be, or any rate limits. This is a significant gap for a tool with zero annotation coverage.

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 directly states the tool's function without any unnecessary words. It's front-loaded with the core action and resource, making it easy to parse and understand quickly.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate as a basic listing function. However, it lacks details on behavioral aspects like safety, output format, or integration with siblings, which could enhance completeness for an AI agent in this context-rich server.

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 has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline expectation for a parameterless tool. No additional value is required beyond stating the purpose.

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 action ('List') and target resource ('all configured AI endpoints available for bridge creation'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'listAIBridges' or 'testAIConnection', which prevents a perfect score.

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 'listAIBridges' or 'createAIBridge'. It mentions 'available for bridge creation', which implies a context but doesn't specify prerequisites, timing, or exclusions, leaving the agent with minimal usage direction.

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