Skip to main content
Glama

tcp_proxy_delete

Delete a TCP proxy from Railway infrastructure to remove unused proxies, manage security, and perform endpoint cleanup. Use this tool for permanent proxy removal.

Instructions

[API] Delete a TCP proxy

⚡️ Best for: ✓ Removing unused proxies ✓ Security management ✓ Endpoint cleanup

⚠️ Not for: × Temporary proxy disabling × Port updates

→ Prerequisites: tcp_proxy_list

→ Related: service_update

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proxyIdYesID of the TCP proxy to delete

Implementation Reference

  • The handler function that executes the tcp_proxy_delete tool logic by calling tcpProxyService.deleteTcpProxy(proxyId).
    async ({ proxyId }) => {
      return tcpProxyService.deleteTcpProxy(proxyId);
    }
  • Input schema using Zod for the tcp_proxy_delete tool, requiring a proxyId string.
    {
      proxyId: z.string().describe("ID of the TCP proxy to delete")
    },
  • Registration of the tcp_proxy_delete tool using createTool, including description, schema, and handler.
    createTool(
      "tcp_proxy_delete",
      formatToolDescription({
        type: 'API',
        description: "Delete a TCP proxy",
        bestFor: [
          "Removing unused proxies",
          "Security management",
          "Endpoint cleanup"
        ],
        notFor: [
          "Temporary proxy disabling",
          "Port updates"
        ],
        relations: {
          prerequisites: ["tcp_proxy_list"],
          related: ["service_update"]
        }
      }),
      {
        proxyId: z.string().describe("ID of the TCP proxy to delete")
      },
      async ({ proxyId }) => {
        return tcpProxyService.deleteTcpProxy(proxyId);
      }
    )
  • Helper service method deleteTcpProxy that wraps the repository call and handles responses/errors.
    async deleteTcpProxy(id: string): Promise<CallToolResult> {
      try {
        const result = await this.client.tcpProxies.tcpProxyDelete(id);
        
        if (result) {
          return createSuccessResponse({
            text: `TCP Proxy with ID ${id} deleted successfully`,
            data: { success: true }
          });
        } else {
          return createErrorResponse(`Failed to delete TCP Proxy with ID ${id}`);
        }
      } catch (error) {
        return createErrorResponse(`Error deleting TCP proxy: ${formatError(error)}`);
      }
    }
  • Repository helper that executes the GraphQL mutation to delete the TCP proxy.
    async tcpProxyDelete(id: string): Promise<boolean> {
      const query = `
        mutation tcpProxyDelete($id: String!) {
          tcpProxyDelete(id: $id)
        }
      `;
    
      const variables = { id };
      const response = await this.client.request<{ tcpProxyDelete: boolean }>(query, variables);
      return response.tcpProxyDelete;
    }
Behavior3/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 correctly identifies this as a destructive operation ('Delete'), which is appropriate. However, it doesn't mention important behavioral aspects like whether deletion is permanent/irreversible, what happens to associated resources, authentication requirements, or error conditions. The description adds some context about use cases but misses key operational details.

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 extremely well-structured and concise, using bullet points, icons, and clear sections that make information easy to scan. Every sentence earns its place by providing specific guidance without redundancy. The information is front-loaded with the core purpose, followed by usage guidelines and related context.

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

Completeness4/5

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

For a single-parameter destructive operation with no annotations and no output schema, the description provides good contextual completeness. It covers purpose, usage scenarios, exclusions, prerequisites, and related tools. The main gap is the lack of information about the deletion consequences (permanence, side effects) and what the tool returns, but given the schema covers the parameter well and the description provides strong usage guidance, it's reasonably complete.

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 the single parameter 'proxyId' well-documented in the schema. The description doesn't add any additional parameter information beyond what's already in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 resource ('a TCP proxy'), making the purpose immediately understandable. It distinguishes from sibling tools like tcp_proxy_create and tcp_proxy_list by focusing on removal rather than creation or listing. However, it doesn't explicitly differentiate from other deletion tools like service_delete or volume_delete beyond the resource type.

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

Usage Guidelines5/5

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

The description provides excellent usage guidance with explicit 'Best for' and 'Not for' sections, clearly indicating when to use this tool (removing unused proxies, security management, endpoint cleanup) and when not to use it (temporary proxy disabling, port updates). It also mentions prerequisites (tcp_proxy_list) and related tools (service_update), offering comprehensive context for decision-making.

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/epitaphe360/railway-mcp'

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