Skip to main content
Glama

send_websocket_data

Send data payloads to connected WebSocket clients in SpyNet mock servers for real-time communication during application testing and development.

Instructions

Send a data message to connected WebSocket client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession identifier
dataYesData payload to send

Implementation Reference

  • Implementation of the send_websocket_data tool handler.
    send_websocket_data: async (args: any) => {
      try {
        const { sessionId, data } = args;
    
        if (!sessionId || data === undefined) {
          return {
            success: false,
            error: 'Missing required fields: sessionId, data'
          };
        }
    
        const sent = wsHub.sendData(sessionId, data);
    
        if (!sent) {
          return {
            success: false,
            error: 'No active connection for session'
          };
        }
    
        return { success: true };
      } catch (error: any) {
        return {
          success: false,
          error: `Failed to send data: ${error.message}`
        };
      }
    }
  • Registration and schema definition for the send_websocket_data tool.
    name: 'send_websocket_data',
    description: 'Send a data message to connected WebSocket client',
    inputSchema: {
      type: 'object',
      properties: {
        sessionId: {
          type: 'string',
          description: 'Session identifier',
        },
        data: {
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose critical WebSocket behavioral traits: what happens if the client is disconnected, whether the operation blocks, payload size limits, or success/failure return semantics. Only states the obvious send operation.

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?

Single 9-word sentence is front-loaded and contains no waste. However, it is arguably underspecified for a networking tool rather than appropriately concise—missing critical behavioral context that would help an agent handle errors.

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?

For a WebSocket communication tool with no annotations and no output schema, the description is incomplete. Lacks connection state requirements, error handling details, payload constraints, and differentiation from send_websocket_action that are necessary for correct invocation.

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 has 100% description coverage (sessionId and data both documented), establishing baseline 3. Description adds no additional parameter semantics, examples, or format constraints beyond what the schema already provides.

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?

Clearly states the verb (Send) and resource (data message to WebSocket client). Specifies 'data message' which implicitly distinguishes from sibling tool send_websocket_action, though it could explicitly clarify the semantic difference between a 'data message' and an 'action'.

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?

Provides no guidance on when to use this vs send_websocket_action, nor prerequisites like requiring an active session/connection before sending. No mention of error conditions or failure modes.

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/aj-bartocci/SpyNet'

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