Skip to main content
Glama
jim-coyne

Hyperfabric MCP Server

vnisDeleteFabricVniMember

Remove a specific member from a VNI in network fabric infrastructure to manage connectivity and resource allocation.

Instructions

Delete a specific VNI member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fabricIdYesThe fabric id or name.
vniIdYesThe VNI id or name.
memberIdYesThe member id or name.

Implementation Reference

  • Core handler that implements the execution logic for all tools, including 'vnisDeleteFabricVniMember'. It resolves the tool name to the corresponding OpenAPI path/method, constructs the HTTP request from arguments, and calls the Hyperfabric REST API endpoint.
    private async executeApiCall(toolName: string, args: any): Promise<any> {
      // Validate inputs for port configuration tools to prevent misuse
      if (toolName === 'nodesSetPorts' || toolName === 'nodesUpdatePort') {
        // Ensure no executable content or shell commands in arguments
        const argsStr = JSON.stringify(args);
        if (/(\$\(|`|eval|exec|system|spawn|child_process)/.test(argsStr)) {
          throw new Error('Security: Invalid arguments detected. Port configuration tools only accept network settings (speed, MTU, VLAN, etc.)');
        }
      }
      
      // Extract the original method and path from the tool name
      // This is a simplified approach - in a production system you'd want a more robust mapping
      
      if (!this.openApiSpec?.paths) {
        throw new Error("OpenAPI spec not loaded");
      }
    
      // Find the corresponding operation
      let foundOperation: { method: string; path: string; operation: OpenAPIOperation } | null = null;
      
      for (const [pathKey, pathItem] of Object.entries(this.openApiSpec.paths)) {
        for (const [method, operation] of Object.entries(pathItem)) {
          if (typeof operation !== 'object' || !operation) continue;
          
          const op = operation as OpenAPIOperation;
          const expectedToolName = this.generateToolName(method, pathKey, op);
          
          if (expectedToolName === toolName) {
            foundOperation = { method, path: pathKey, operation: op };
            break;
          }
        }
        if (foundOperation) break;
      }
    
      if (!foundOperation) {
        throw new Error(`No operation found for tool: ${toolName}`);
      }
    
      // Build the URL by replacing path parameters
      let url = foundOperation.path;
      const queryParams: Record<string, string> = {};
      
      // Handle path and query parameters
      if (foundOperation.operation.parameters) {
        for (const param of foundOperation.operation.parameters) {
          const value = args[param.name];
          if (value !== undefined) {
            if (param.in === 'path') {
              url = url.replace(`{${param.name}}`, encodeURIComponent(value));
            } else if (param.in === 'query') {
              queryParams[param.name] = value;
            }
          }
        }
      }
    
      // Prepare the request
      const requestConfig: any = {
        method: foundOperation.method.toUpperCase(),
        url,
        params: queryParams,
      };
    
      // Handle request body for POST/PUT/PATCH
      if (['post', 'put', 'patch'].includes(foundOperation.method.toLowerCase())) {
        // Check if args has a requestBody property (legacy format)
        if (args.requestBody) {
          requestConfig.data = args.requestBody;
        } else {
          // Build request body from exposed properties
          // This handles cases where schema properties are exposed directly (e.g., fabrics, nodes, etc.)
          const requestBody: Record<string, any> = {};
          const pathItem = this.openApiSpec?.paths?.[foundOperation.path];
          const operation = (pathItem as any)?.[foundOperation.method];
          
          if (operation?.requestBody) {
            const requestBodyDef = this.resolveSchemaRef(operation.requestBody);
            const schema = this.deepResolveSchema(requestBodyDef.content?.['application/json']?.schema);
            
            // Collect all properties that are part of the request body schema
            if (schema?.properties) {
              for (const propName of Object.keys(schema.properties)) {
                if (args.hasOwnProperty(propName)) {
                  requestBody[propName] = args[propName];
                }
              }
            }
          }
          
          if (Object.keys(requestBody).length > 0) {
            requestConfig.data = requestBody;
          }
        }
      }
    
      logger.debug(`Making API call: ${requestConfig.method} ${url}`);
      
      try {
        const response = await this.httpClient.request(requestConfig);
        return {
          status: response.status,
          statusText: response.statusText,
          data: response.data
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`API call failed: ${error.response?.status} ${error.response?.statusText} - ${JSON.stringify(error.response?.data)}`);
        }
        throw error;
      }
    }
  • src/main.ts:134-158 (registration)
    Dynamically generates and registers all tools (including 'vnisDeleteFabricVniMember') from the OpenAPI specification by iterating over paths and methods, creating Tool objects, and adding them to this.tools list used by MCP listTools handler.
    private generateTools(): void {
      if (!this.openApiSpec?.paths) {
        logger.error("No paths found in OpenAPI spec");
        return;
      }
    
      this.tools = [];
    
      for (const [pathKey, pathItem] of Object.entries(this.openApiSpec.paths)) {
        for (const [method, operation] of Object.entries(pathItem)) {
          if (typeof operation !== 'object' || !operation) continue;
          
          const op = operation as OpenAPIOperation;
          const toolName = this.generateToolName(method, pathKey, op);
          const tool = this.createToolFromOperation(toolName, method, pathKey, op);
          
          if (tool) {
            this.tools.push(tool);
            logger.debug(`Generated tool: ${toolName}`);
          }
        }
      }
    
      logger.info(`Generated ${this.tools.length} tools from OpenAPI spec`);
    }
  • Generates the inputSchema and Tool definition for 'vnisDeleteFabricVniMember' (and all tools) by extracting parameters from path/query and flattening requestBody properties from the OpenAPI operation.
    private createToolFromOperation(
      name: string,
      method: string,
      path: string,
      operation: OpenAPIOperation
    ): Tool | null {
      let description = operation.summary || operation.description || `${method.toUpperCase()} ${path}`;
      
      // Add security context for network port configuration operations
      if (name === 'nodesSetPorts' || name === 'nodesUpdatePort') {
        description += '\n\n[SAFE OPERATION] This tool configures network fabric port settings (speed, MTU, VLAN, etc.) via REST API. It does NOT execute code or commands on the system.';
      }
      
      // Enhance description for create/update operations
      if (['post', 'put', 'patch'].includes(method.toLowerCase())) {
        if (method.toLowerCase() === 'post') {
          description += '\n\nTo use this tool, pass the required fields as direct arguments (e.g., fabrics=[{name:"my-fabric", description:"...", ...}])';
        } else if (method.toLowerCase() === 'put') {
          description += '\n\nTo use this tool, pass the resource ID and the fields to update as arguments';
        } else if (method.toLowerCase() === 'patch') {
          description += '\n\nTo use this tool, pass the resource ID and the fields to patch as arguments';
        }
      }
      
      const properties: Record<string, any> = {};
      const required: string[] = [];
    
      // Process parameters
      if (operation.parameters) {
        for (const param of operation.parameters) {
          if (param.in === 'path' || param.in === 'query') {
            properties[param.name] = {
              type: param.schema?.type || 'string',
              description: param.description || ''
            };
            
            if (param.required) {
              required.push(param.name);
            }
          }
        }
      }
    
      // Process request body for POST/PUT/PATCH requests
      if (operation.requestBody && ['post', 'put', 'patch'].includes(method.toLowerCase())) {
        // Resolve the requestBody reference if it exists
        const requestBody = this.resolveSchemaRef(operation.requestBody);
        const content = requestBody.content;
        
        if (content?.['application/json']?.schema) {
          let schema = content['application/json'].schema;
          // Deeply resolve schema references
          schema = this.deepResolveSchema(schema);
          
          if (schema.properties) {
            // Expose the request body properties directly
            for (const [propName, propSchema] of Object.entries(schema.properties)) {
              const propDef = propSchema as any;
              properties[propName] = this.deepResolveSchema(propDef, 0);
              
              if (schema.required?.includes(propName)) {
                required.push(propName);
              }
            }
          }
        }
      }
    
      return {
        name,
        description,
        inputSchema: {
          type: 'object',
          properties,
          required
        }
      };
    }
  • Generates the tool name for registration and lookup. For 'vnisDeleteFabricVniMember', this uses the operationId from the OpenAPI spec if present, otherwise derives from path and method.
    private generateToolName(method: string, path: string, operation: OpenAPIOperation): string {
      if (operation.operationId) {
        return operation.operationId;
      }
    
      // Generate a name from the method and path
      const pathParts = path.split('/').filter(part => part && !part.startsWith('{'));
      const nameBase = pathParts.join('_').replace(/[^a-zA-Z0-9_]/g, '_');
      return `${method}_${nameBase}`;
    }
  • src/main.ts:292-335 (registration)
    Registers the MCP protocol handlers: listTools returns the generated tools list, callTool dispatches to executeApiCall based on tool name.
    private setupHandlers(): void {
      this.server.setRequestHandler(ListToolsRequestSchema, async () => {
        return { tools: this.tools };
      });
    
      this.server.setRequestHandler(CallToolRequestSchema, async (request: any) => {
        const { name, arguments: args } = request.params;
        
        logger.info(`Calling tool: ${name}`);
        logger.debug(`Tool arguments: ${JSON.stringify(args, null, 2)}`);
        
        try {
          // Find the tool definition
          const tool = this.tools.find(t => t.name === name);
          if (!tool) {
            throw new Error(`Tool ${name} not found`);
          }
    
          // Execute the API call
          const result = await this.executeApiCall(name, args);
          
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(result, null, 2)
              }
            ]
          };
        } catch (error) {
          logger.error(`Error executing tool ${name}:`, error);
          
          return {
            content: [
              {
                type: "text",
                text: `Error: ${error instanceof Error ? error.message : String(error)}`
              }
            ],
            isError: true
          };
        }
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this operation is reversible, what permissions are required, or what happens on success/failure (e.g., error if member doesn't exist). For a destructive tool with zero annotation coverage, this is a significant gap in safety and operational context.

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 any fluff. It's front-loaded with the key action ('Delete') and target, making it easy to parse. Every word earns its place, and there's no wasted verbiage.

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 tool's destructive nature, lack of annotations, and absence of an output schema, the description is incomplete. It doesn't cover behavioral aspects like idempotency, error conditions, or return values. For a deletion operation with three required parameters, more context is needed to ensure safe and correct usage by an agent.

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%, with clear descriptions for 'fabricId', 'vniId', and 'memberId' in the input schema. The description adds no additional parameter semantics beyond what's already documented in the schema (e.g., format examples or relationships between parameters). With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 ('Delete') and the target ('a specific VNI member'), which is a specific verb+resource combination. It distinguishes from sibling tools like 'vnisDeleteFabricVni' (which deletes the entire VNI) by specifying 'member' deletion. However, it doesn't explicitly mention the resource hierarchy (fabric→VNI→member), which could be slightly more specific.

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. It doesn't mention prerequisites (e.g., the member must exist), related operations (e.g., use 'vnisGetFabricVniMember' to check first), or sibling tools like 'vnisAddFabricVniMembers' for adding members. Without this context, an agent might struggle with proper sequencing.

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/jim-coyne/hyperfabric_MCP'

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