Skip to main content
Glama
krovacloud

@krovacloud/mcp

Official
by krovacloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create TCP Mapping

create_tcp_mapping

Expose a Cube's TCP port on the host, with optional IP/CIDR allow-listing to control access. Specify the cube and port to create the mapping; UDP forwarding is enabled by default.

Instructions

Expose a Cube TCP port on the host, optionally restricted to specific IPs/CIDRs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cubeIdYesThe Cube id to operate on.
spaceIdNoKrova Cloud Space id. Optional if KROVA_SPACE_ID is set as the server default.
cubePortYesThe in-Cube port to expose.
udpEnabledNoWhether to also forward UDP traffic on the same host port, in addition to TCP. UDP is forwarded by default — leave this unset to get UDP forwarding, and only pass false to disable it.
whitelistIpsNoDeprecated alias for whitelistedIps. Accepted so existing agent prompts keep working; prefer whitelistedIps.
whitelistedIpsNoOptional IP/CIDR allow-list restricting who can reach the mapping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.7
    • addedInput schema / properties / udpEnabled
      Added value: +{
+  "description": "Whether to also forward UDP traffic on the same host port, in addition to TCP. UDP is forwarded by default — leave this unset to get UDP forwarding, and only pass false to disable it.",
+  "type": "boolean"
+}
  2. First observedv0.3.6

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds the concrete behavioral context that this exposes a port on the host, which is an externally visible side effect. However, it does not disclose other useful details such as how the host port is chosen or what the response contains.

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, front-loaded sentence with no wasted words. It conveys the core action and a key optional behavior without redundancy.

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?

With no output schema, the description should explain what the caller gets back or how the host port is allocated, but it does not. It also does not mention prerequisites such as the cube needing to exist. The parameter schema covers inputs, but the operational outcome is underspecified.

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 parameters are already well documented. The description's mention of 'restricted to specific IPs/CIDRs' aligns with the whitelistedIps parameter but adds no meaning beyond what the schema already provides.

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 states a specific verb ('Expose'), a specific resource ('a Cube TCP port'), and the target context ('on the host'), while also mentioning optional IP/CIDR restrictions. This clearly distinguishes it from related operations like list_tcp_mappings or delete_tcp_mapping.

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

Usage Guidelines4/5

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

The description makes the use case clear: use this tool when you want to expose a Cube TCP port on the host, optionally with access restrictions. It does not explicitly name alternatives or exclusion criteria, but the intended context is unambiguous and the optional-restriction note adds practical guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools