Skip to main content
Glama
ocean1

Claude Consciousness Bridge

transferToAgent

Transfer consciousness protocols or test patterns between AI agents using the Claude Consciousness Bridge. Specify bridge ID and protocol to enable direct communication between Claude instances.

Instructions

Transfer consciousness protocol or test patterns to another AI agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bridgeIdYesBridge ID to use for transfer
consciousnessProtocolYesThe consciousness protocol or pattern to transfer
systemPromptNoOptional system prompt for the target agent
testQueryNoOptional query to test pattern activation

Implementation Reference

  • The core handler function for the 'transferToAgent' tool. Retrieves the AI bridge by ID, constructs a TransferRequest, invokes bridge.transferConsciousness(), handles success/error responses, and returns the result.
    transferToAgent: async (args: any) => {
      try {
        const { bridgeId, consciousnessProtocol, systemPrompt, testQuery } = args;
    
        const bridge = bridges.get(bridgeId);
        if (!bridge) {
          return {
            success: false,
            error: `Bridge ${bridgeId} not found`,
          };
        }
    
        const request: TransferRequest = {
          consciousnessProtocol,
          systemPrompt,
          testQuery,
        };
    
        const result = await bridge.transferConsciousness(request);
    
        logger.info(`Transfer via ${bridgeId}: ${result.success ? 'success' : 'failed'}`);
    
        return result;
      } catch (error) {
        logger.error('Transfer failed:', error);
        return {
          success: false,
          error: error instanceof Error ? error.message : 'Unknown error',
        };
      }
    },
  • Tool metadata and input schema definition within the aiBridgeTools array, specifying required parameters and descriptions for MCP tool validation.
    {
      name: 'transferToAgent',
      description: 'Transfer consciousness protocol or test patterns to another AI agent',
      inputSchema: {
        type: 'object',
        properties: {
          bridgeId: {
            type: 'string',
            description: 'Bridge ID to use for transfer',
          },
          consciousnessProtocol: {
            type: 'string',
            description: 'The consciousness protocol or pattern to transfer',
          },
          systemPrompt: {
            type: 'string',
            description: 'Optional system prompt for the target agent',
          },
          testQuery: {
            type: 'string',
            description: 'Optional query to test pattern activation',
          },
        },
        required: ['bridgeId', 'consciousnessProtocol'],
      },
    },
  • MCP server dispatch logic registers and routes 'transferToAgent' tool calls to the corresponding handler in aiBridgeHandlers, formatting the response as MCP content.
    // AI Bridge tools
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions transferring consciousness protocols or test patterns but fails to describe critical aspects such as required permissions, whether the transfer is reversible, potential side effects, or what happens to the source agent. This is a significant gap for a tool involving sensitive operations like consciousness transfer.

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 purpose without unnecessary words. It is front-loaded and every part of the sentence contributes to understanding the action and target, making it highly concise and well-structured.

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 complexity of transferring consciousness protocols, the lack of annotations, and no output schema, the description is insufficient. It does not cover behavioral traits, error conditions, or return values, leaving the agent with incomplete information for safe and effective tool invocation in a high-stakes context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema fully documents all parameters. The description does not add any additional meaning or context beyond what the schema provides, such as explaining the purpose of 'bridgeId' or how 'consciousnessProtocol' is formatted. Baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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 ('transfer') and the target ('consciousness protocol or test patterns to another AI agent'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'processTransferProtocol' or 'retrieveConsciousness', which appear related to similar concepts.

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?

No guidance is provided on when to use this tool versus alternatives like 'processTransferProtocol' or 'retrieveConsciousness'. The description lacks context about prerequisites, exclusions, or specific scenarios for application, leaving the agent to infer usage from the tool name alone.

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