Skip to main content
Glama
ahmedselimmansor-ctrl

IBM Cloud MCP Server

dl_create_gateway

Create a Direct Link gateway to establish dedicated or connect type connectivity with bandwidth, BGP ASN, and location.

Instructions

Create a Direct Link gateway

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
typeYes
speed_mbpsYesSpeed in Mbps
bgp_asnYesBGP ASN
location_nameNo
cross_connect_routerNo

Implementation Reference

  • Handler that creates a Direct Link gateway via POST to IBM Cloud Direct Link API. Validates input with Zod schema, checks write permission via w(), and sends name, type, speed_mbps, bgp_asn, optional location_name and cross_connect_router.
    server.tool("dl_create_gateway", "Create a Direct Link gateway", {
      name: z.string(), type: z.enum(["dedicated","connect"]),
      speed_mbps: z.number().describe("Speed in Mbps"), bgp_asn: z.number().describe("BGP ASN"),
      location_name: z.string().optional(), cross_connect_router: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${dl}/gateways`, {
        name:p.name, type:p.type, speed_mbps:p.speed_mbps, bgp_asn:p.bgp_asn,
        location_name:p.location_name, cross_connect_router:p.cross_connect_router,
      }, {version:"2024-03-01"});
    }));
  • Zod schema defining the input parameters for dl_create_gateway: name (string), type (enum: dedicated|connect), speed_mbps (number), bgp_asn (number), location_name (optional string), cross_connect_router (optional string).
      name: z.string(), type: z.enum(["dedicated","connect"]),
      speed_mbps: z.number().describe("Speed in Mbps"), bgp_asn: z.number().describe("BGP ASN"),
      location_name: z.string().optional(), cross_connect_router: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
  • Registration of the dl_create_gateway tool via server.tool(), inside the registerNetworkingTools function which is called from src/server.ts.
    server.tool("dl_create_gateway", "Create a Direct Link gateway", {
      name: z.string(), type: z.enum(["dedicated","connect"]),
      speed_mbps: z.number().describe("Speed in Mbps"), bgp_asn: z.number().describe("BGP ASN"),
      location_name: z.string().optional(), cross_connect_router: z.string().optional(),
    }, async (p) => safeTool(async () => { w();
      return client.post(`${dl}/gateways`, {
        name:p.name, type:p.type, speed_mbps:p.speed_mbps, bgp_asn:p.bgp_asn,
        location_name:p.location_name, cross_connect_router:p.cross_connect_router,
      }, {version:"2024-03-01"});
    }));
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as idempotency, permissions required, or side effects. The single sentence only states the action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is short, it is too terse to be useful. It sacrifices necessary detail for brevity, making it inadequate for a tool with six parameters.

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

Completeness1/5

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

Given the complexity of a creation tool with multiple parameters and no output schema, this description is severely incomplete. It provides no return value info, no parameter explanations, and no usage context.

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

Parameters1/5

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

The description adds no information about parameters. With only 33% schema description coverage, the agent receives no help understanding required or optional fields beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a 'Direct Link gateway', which is a specific resource. The tool name also echoes this, making it unambiguous.

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 on when to use this tool versus alternatives like dl_list_gateways or tg_create_gateway. Lacks context on prerequisites or appropriate scenarios.

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/ahmedselimmansor-ctrl/IBM_cloud_MCP_SERVER'

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