@vercel/sdk 1.4.0 → 1.6.0

package/esm/mcp-server/tools/artifactsArtifactExists.js

@@ -8,7 +8,7 @@ const args = {
     request: ArtifactExistsRequest$inboundSchema,
 };
 export const tool$artifactsArtifactExists = {
-    name: "artifacts_artifact-exists",
+    name: "artifacts-artifact-exists",
     description: `Check if a cache artifact exists
 
 Check that a cache artifact with the given \`hash\` exists. This request returns response headers only and is equivalent to a \`GET\` request to this endpoint where the response contains no body.`,

package/esm/mcp-server/tools/artifactsArtifactQuery.js

@@ -8,7 +8,7 @@ const args = {
     request: ArtifactQueryRequest$inboundSchema,
 };
 export const tool$artifactsArtifactQuery = {
-    name: "artifacts_artifact-query",
+    name: "artifacts-artifact-query",
     description: `Query information about an artifact
 
 Query information about an array of artifacts.`,

package/esm/mcp-server/tools/artifactsDownloadArtifact.js

@@ -8,7 +8,7 @@ const args = {
     request: DownloadArtifactRequest$inboundSchema,
 };
 export const tool$artifactsDownloadArtifact = {
-    name: "artifacts_download-artifact",
+    name: "artifacts-download-artifact",
     description: `Download a cache artifact
 
 Downloads a cache artifact indentified by its \`hash\` specified on the request path. The artifact is downloaded as an octet-stream. The client should verify the content-length header and response body.`,

package/esm/mcp-server/tools/artifactsRecordEvents.js

@@ -8,7 +8,7 @@ const args = {
     request: RecordEventsRequest$inboundSchema,
 };
 export const tool$artifactsRecordEvents = {
-    name: "artifacts_record-events",
+    name: "artifacts-record-events",
     description: `Record an artifacts cache usage event
 
 Records an artifacts cache usage event. The body of this request is an array of cache usage events. The supported event types are \`HIT\` and \`MISS\`. The source is either \`LOCAL\` the cache event was on the users filesystem cache or \`REMOTE\` if the cache event is for a remote cache. When the event is a \`HIT\` the request also accepts a number \`duration\` which is the time taken to generate the artifact in the cache.`,

package/esm/mcp-server/tools/artifactsStatus.js

@@ -8,7 +8,7 @@ const args = {
     request: StatusRequest$inboundSchema,
 };
 export const tool$artifactsStatus = {
-    name: "artifacts_status",
+    name: "artifacts-status",
     description: `Get status of Remote Caching for this principal
 
 Check the status of Remote Caching for this principal. Returns a JSON-encoded status indicating if Remote Caching is enabled, disabled, or disabled due to usage limits.`,

package/esm/mcp-server/tools/artifactsUploadArtifact.js

@@ -8,7 +8,7 @@ const args = {
     request: UploadArtifactRequest$inboundSchema,
 };
 export const tool$artifactsUploadArtifact = {
-    name: "artifacts_upload-artifact",
+    name: "artifacts-upload-artifact",
     description: `Upload a cache artifact
 
 Uploads a cache artifact identified by the \`hash\` specified on the path. The cache artifact can then be downloaded with the provided \`hash\`.`,

package/esm/mcp-server/tools/authenticationCreateAuthToken.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateAuthTokenRequest$inboundSchema,
 };
 export const tool$authenticationCreateAuthToken = {
-    name: "authentication_create-auth-token",
+    name: "authentication-create-auth-token",
     description: `Create an Auth Token
 
 Creates and returns a new authentication token for the currently authenticated User. The \`bearerToken\` property is only provided once, in the response body, so be sure to save it on the client for use with API requests.`,

package/esm/mcp-server/tools/authenticationDeleteAuthToken.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteAuthTokenRequest$inboundSchema,
 };
 export const tool$authenticationDeleteAuthToken = {
-    name: "authentication_delete-auth-token",
+    name: "authentication-delete-auth-token",
     description: `Delete an authentication token
 
 Invalidate an authentication token, such that it will no longer be valid for future HTTP requests.`,

package/esm/mcp-server/tools/authenticationExchangeSsoToken.js

@@ -8,7 +8,7 @@ const args = {
     request: ExchangeSsoTokenRequestBody$inboundSchema,
 };
 export const tool$authenticationExchangeSsoToken = {
-    name: "authentication_exchange-sso-token",
+    name: "authentication-exchange-sso-token",
     description: `SSO Token Exchange
 
 During the autorization process, Vercel sends the user to the provider [redirectLoginUrl](https://vercel.com/docs/integrations/create-integration/submit-integration#redirect-login-url), that includes the OAuth authorization \`code\` parameter. The provider then calls the SSO Token Exchange endpoint with the sent code and receives the OIDC token. They log the user in based on this token and redirects the user back to the Vercel account using deep-link parameters included the redirectLoginUrl. This is used to verify the identity of the user during the [**Open in Provider** flow](https://vercel.com/docs/integrations/marketplace-flows#open-in-provider-button-flow). Providers should not persist the returned \`id_token\` in a database since the token will expire.`,

package/esm/mcp-server/tools/authenticationGetAuthToken.js

@@ -8,7 +8,7 @@ const args = {
     request: GetAuthTokenRequest$inboundSchema,
 };
 export const tool$authenticationGetAuthToken = {
-    name: "authentication_get-auth-token",
+    name: "authentication-get-auth-token",
     description: `Get Auth Token Metadata
 
 Retrieve metadata about an authentication token belonging to the currently authenticated User.`,

package/esm/mcp-server/tools/authenticationListAuthTokens.js

@@ -4,7 +4,7 @@
 import { authenticationListAuthTokens } from "../../funcs/authenticationListAuthTokens.js";
 import { formatResult } from "../tools.js";
 export const tool$authenticationListAuthTokens = {
-    name: "authentication_list-auth-tokens",
+    name: "authentication-list-auth-tokens",
     description: `List Auth Tokens
 
 Retrieve a list of the current User's authentication tokens.`,

package/esm/mcp-server/tools/certsGetCertById.js

@@ -8,7 +8,7 @@ const args = {
     request: GetCertByIdRequest$inboundSchema,
 };
 export const tool$certsGetCertById = {
-    name: "certs_get-cert-by-id",
+    name: "certs-get-cert-by-id",
     description: `Get cert by id
 
 Get cert by id`,

package/esm/mcp-server/tools/certsIssueCert.js

@@ -8,7 +8,7 @@ const args = {
     request: IssueCertRequest$inboundSchema,
 };
 export const tool$certsIssueCert = {
-    name: "certs_issue-cert",
+    name: "certs-issue-cert",
     description: `Issue a new cert
 
 Issue a new cert`,

package/esm/mcp-server/tools/certsRemoveCert.js

@@ -8,7 +8,7 @@ const args = {
     request: RemoveCertRequest$inboundSchema,
 };
 export const tool$certsRemoveCert = {
-    name: "certs_remove-cert",
+    name: "certs-remove-cert",
     description: `Remove cert
 
 Remove cert`,

package/esm/mcp-server/tools/certsUploadCert.js

@@ -8,7 +8,7 @@ const args = {
     request: UploadCertRequest$inboundSchema,
 };
 export const tool$certsUploadCert = {
-    name: "certs_upload-cert",
+    name: "certs-upload-cert",
     description: `Upload a cert
 
 Upload a cert`,

package/esm/mcp-server/tools/checksCreateCheck.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateCheckRequest$inboundSchema,
 };
 export const tool$checksCreateCheck = {
-    name: "checks_create-check",
+    name: "checks-create-check",
     description: `Creates a new Check
 
 Creates a new check. This endpoint must be called with an OAuth2 or it will produce a 400 error.`,

package/esm/mcp-server/tools/checksGetAllChecks.js

@@ -8,7 +8,7 @@ const args = {
     request: GetAllChecksRequest$inboundSchema,
 };
 export const tool$checksGetAllChecks = {
-    name: "checks_get-all-checks",
+    name: "checks-get-all-checks",
     description: `Retrieve a list of all checks
 
 List all of the checks created for a deployment.`,

package/esm/mcp-server/tools/checksGetCheck.js

@@ -8,7 +8,7 @@ const args = {
     request: GetCheckRequest$inboundSchema,
 };
 export const tool$checksGetCheck = {
-    name: "checks_get-check",
+    name: "checks-get-check",
     description: `Get a single check
 
 Return a detailed response for a single check.`,

package/esm/mcp-server/tools/checksRerequestCheck.js

@@ -8,7 +8,7 @@ const args = {
     request: RerequestCheckRequest$inboundSchema,
 };
 export const tool$checksRerequestCheck = {
-    name: "checks_rerequest-check",
+    name: "checks-rerequest-check",
     description: `Rerequest a check
 
 Rerequest a selected check that has failed.`,

package/esm/mcp-server/tools/checksUpdateCheck.js

@@ -8,7 +8,7 @@ const args = {
     request: UpdateCheckRequest$inboundSchema,
 };
 export const tool$checksUpdateCheck = {
-    name: "checks_update-check",
+    name: "checks-update-check",
     description: `Update a check
 
 Update an existing check. This endpoint must be called with an OAuth2 or it will produce a 400 error.`,

package/esm/mcp-server/tools/deploymentsCancelDeployment.js

@@ -8,7 +8,7 @@ const args = {
     request: CancelDeploymentRequest$inboundSchema,
 };
 export const tool$deploymentsCancelDeployment = {
-    name: "deployments_cancel-deployment",
+    name: "deployments-cancel-deployment",
     description: `Cancel a deployment
 
 This endpoint allows you to cancel a deployment which is currently building, by supplying its \`id\` in the URL.`,

package/esm/mcp-server/tools/deploymentsCreateDeployment.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateDeploymentRequest$inboundSchema,
 };
 export const tool$deploymentsCreateDeployment = {
-    name: "deployments_create-deployment",
+    name: "deployments-create-deployment",
     description: `Create a new deployment
 
 Create a new deployment with all the required and intended data. If the deployment is not a git deployment, all files must be provided with the request, either referenced or inlined. Additionally, a deployment id can be specified to redeploy a previous deployment.`,

package/esm/mcp-server/tools/deploymentsDeleteDeployment.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteDeploymentRequest$inboundSchema,
 };
 export const tool$deploymentsDeleteDeployment = {
-    name: "deployments_delete-deployment",
+    name: "deployments-delete-deployment",
     description: `Delete a Deployment
 
 This API allows you to delete a deployment, either by supplying its \`id\` in the URL or the \`url\` of the deployment as a query parameter. You can obtain the ID, for example, by listing all deployments.`,

package/esm/mcp-server/tools/deploymentsGetDeployment.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDeploymentRequest$inboundSchema,
 };
 export const tool$deploymentsGetDeployment = {
-    name: "deployments_get-deployment",
+    name: "deployments-get-deployment",
     description: `Get a deployment by ID or URL
 
 Retrieves information for a deployment either by supplying its ID (\`id\` property) or Hostname (\`url\` property). Additional details will be included when the authenticated user or team is an owner of the deployment.`,

package/esm/mcp-server/tools/deploymentsGetDeploymentEvents.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDeploymentEventsRequest$inboundSchema,
 };
 export const tool$deploymentsGetDeploymentEvents = {
-    name: "deployments_get-deployment-events",
+    name: "deployments-get-deployment-events",
     description: `Get deployment events
 
 Get the build logs of a deployment by deployment ID and build ID. It can work as an infinite stream of logs or as a JSON endpoint depending on the input parameters.`,

package/esm/mcp-server/tools/deploymentsGetDeploymentFileContents.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDeploymentFileContentsRequest$inboundSchema,
 };
 export const tool$deploymentsGetDeploymentFileContents = {
-    name: "deployments_get-deployment-file-contents",
+    name: "deployments-get-deployment-file-contents",
     description: `Get Deployment File Contents
 
 Allows to retrieve the content of a file by supplying the file identifier and the deployment unique identifier. The response body will contain a JSON response containing the contents of the file encoded as base64.`,

package/esm/mcp-server/tools/deploymentsGetDeployments.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDeploymentsRequest$inboundSchema,
 };
 export const tool$deploymentsGetDeployments = {
-    name: "deployments_get-deployments",
+    name: "deployments-get-deployments",
     description: `List deployments
 
 List deployments under the authenticated user or team. If a deployment hasn't finished uploading (is incomplete), the \`url\` property will have a value of \`null\`.`,

package/esm/mcp-server/tools/deploymentsListDeploymentFiles.js

@@ -8,7 +8,7 @@ const args = {
     request: ListDeploymentFilesRequest$inboundSchema,
 };
 export const tool$deploymentsListDeploymentFiles = {
-    name: "deployments_list-deployment-files",
+    name: "deployments-list-deployment-files",
     description: `List Deployment Files
 
 Allows to retrieve the file structure of the source code of a deployment by supplying the deployment unique identifier. If the deployment was created with the Vercel CLI or the API directly with the \`files\` key, it will have a file tree that can be retrievable.`,

package/esm/mcp-server/tools/deploymentsUpdateIntegrationDeploymentAction.js

@@ -8,7 +8,7 @@ const args = {
     request: UpdateIntegrationDeploymentActionRequest$inboundSchema,
 };
 export const tool$deploymentsUpdateIntegrationDeploymentAction = {
-    name: "deployments_update-integration-deployment-action",
+    name: "deployments-update-integration-deployment-action",
     description: `Update deployment integration action
 
 Updates the deployment integration action for the specified integration installation`,

package/esm/mcp-server/tools/deploymentsUploadFile.js

@@ -8,7 +8,7 @@ const args = {
     request: UploadFileRequest$inboundSchema,
 };
 export const tool$deploymentsUploadFile = {
-    name: "deployments_upload-file",
+    name: "deployments-upload-file",
     description: `Upload Deployment Files
 
 Before you create a deployment you need to upload the required files for that deployment. To do it, you need to first upload each file to this endpoint. Once that's completed, you can create a new deployment with the uploaded files. The file content must be placed inside the body of the request. In the case of a successful response you'll receive a status code 200 with an empty body.`,

package/esm/mcp-server/tools/dnsCreateRecord.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateRecordRequest$inboundSchema,
 };
 export const tool$dnsCreateRecord = {
-    name: "dns_create-record",
+    name: "dns-create-record",
     description: `Create a DNS record
 
 Creates a DNS record for a domain.`,

package/esm/mcp-server/tools/dnsGetRecords.js

@@ -8,7 +8,7 @@ const args = {
     request: GetRecordsRequest$inboundSchema,
 };
 export const tool$dnsGetRecords = {
-    name: "dns_get-records",
+    name: "dns-get-records",
     description: `List existing DNS records
 
 Retrieves a list of DNS records created for a domain name. By default it returns 20 records if no limit is provided. The rest can be retrieved using the pagination options.`,

package/esm/mcp-server/tools/dnsRemoveRecord.js

@@ -8,7 +8,7 @@ const args = {
     request: RemoveRecordRequest$inboundSchema,
 };
 export const tool$dnsRemoveRecord = {
-    name: "dns_remove-record",
+    name: "dns-remove-record",
     description: `Delete a DNS record
 
 Removes an existing DNS record from a domain name.`,

package/esm/mcp-server/tools/dnsUpdateRecord.js

@@ -8,7 +8,7 @@ const args = {
     request: UpdateRecordRequest$inboundSchema,
 };
 export const tool$dnsUpdateRecord = {
-    name: "dns_update-record",
+    name: "dns-update-record",
     description: `Update an existing DNS record
 
 Updates an existing DNS record for a domain name.`,

package/esm/mcp-server/tools/domainsBuyDomain.js

@@ -8,7 +8,7 @@ const args = {
     request: BuyDomainRequest$inboundSchema,
 };
 export const tool$domainsBuyDomain = {
-    name: "domains_buy-domain",
+    name: "domains-buy-domain",
     description: `Purchase a domain
 
 Allows to purchase the specified domain.`,

package/esm/mcp-server/tools/domainsCheckDomainPrice.js

@@ -8,7 +8,7 @@ const args = {
     request: CheckDomainPriceRequest$inboundSchema,
 };
 export const tool$domainsCheckDomainPrice = {
-    name: "domains_check-domain-price",
+    name: "domains-check-domain-price",
     description: `Check the price for a domain
 
 Check the price to purchase a domain and how long a single purchase period is.`,

package/esm/mcp-server/tools/domainsCheckDomainStatus.js

@@ -8,7 +8,7 @@ const args = {
     request: CheckDomainStatusRequest$inboundSchema,
 };
 export const tool$domainsCheckDomainStatus = {
-    name: "domains_check-domain-status",
+    name: "domains-check-domain-status",
     description: `Check a Domain Availability
 
 Check if a domain name is available for purchase.`,

package/esm/mcp-server/tools/domainsCreateOrTransferDomain.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateOrTransferDomainRequest$inboundSchema,
 };
 export const tool$domainsCreateOrTransferDomain = {
-    name: "domains_create-or-transfer-domain",
+    name: "domains-create-or-transfer-domain",
     description: `Register or transfer-in a new Domain
 
 This endpoint is used for adding a new apex domain name with Vercel for the authenticating user. Can also be used for initiating a domain transfer request from an external Registrar to Vercel.`,

package/esm/mcp-server/tools/domainsDeleteDomain.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteDomainRequest$inboundSchema,
 };
 export const tool$domainsDeleteDomain = {
-    name: "domains_delete-domain",
+    name: "domains-delete-domain",
     description: `Remove a domain by name
 
 Delete a previously registered domain name from Vercel. Deleting a domain will automatically remove any associated aliases.`,

package/esm/mcp-server/tools/domainsGetDomain.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDomainRequest$inboundSchema,
 };
 export const tool$domainsGetDomain = {
-    name: "domains_get-domain",
+    name: "domains-get-domain",
     description: `Get Information for a Single Domain
 
 Get information for a single domain in an account or team.`,

package/esm/mcp-server/tools/domainsGetDomainConfig.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDomainConfigRequest$inboundSchema,
 };
 export const tool$domainsGetDomainConfig = {
-    name: "domains_get-domain-config",
+    name: "domains-get-domain-config",
     description: `Get a Domain's configuration
 
 Get a Domain's configuration.`,

package/esm/mcp-server/tools/domainsGetDomainTransfer.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDomainTransferRequest$inboundSchema,
 };
 export const tool$domainsGetDomainTransfer = {
-    name: "domains_get-domain-transfer",
+    name: "domains-get-domain-transfer",
     description: `Get domain transfer info.
 
 Fetch domain transfer availability or transfer status if a transfer is in progress.`,

package/esm/mcp-server/tools/domainsGetDomains.js

@@ -8,7 +8,7 @@ const args = {
     request: GetDomainsRequest$inboundSchema,
 };
 export const tool$domainsGetDomains = {
-    name: "domains_get-domains",
+    name: "domains-get-domains",
     description: `List all the domains
 
 Retrieves a list of domains registered for the authenticated user or team. By default it returns the last 20 domains if no limit is provided.`,

package/esm/mcp-server/tools/domainsPatchDomain.js

@@ -8,7 +8,7 @@ const args = {
     request: PatchDomainRequest$inboundSchema,
 };
 export const tool$domainsPatchDomain = {
-    name: "domains_patch-domain",
+    name: "domains-patch-domain",
     description: `Update or move apex domain
 
 Update or move apex domain.`,

package/esm/mcp-server/tools/edgeConfigCreateEdgeConfig.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateEdgeConfigRequest$inboundSchema,
 };
 export const tool$edgeConfigCreateEdgeConfig = {
-    name: "edge-config_create-edge-config",
+    name: "edge-config-create-edge-config",
     description: `Create an Edge Config
 
 Creates an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigCreateEdgeConfigToken.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateEdgeConfigTokenRequest$inboundSchema,
 };
 export const tool$edgeConfigCreateEdgeConfigToken = {
-    name: "edge-config_create-edge-config-token",
+    name: "edge-config-create-edge-config-token",
     description: `Create an Edge Config token
 
 Adds a token to an existing Edge Config.`,

package/esm/mcp-server/tools/edgeConfigDeleteEdgeConfig.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteEdgeConfigRequest$inboundSchema,
 };
 export const tool$edgeConfigDeleteEdgeConfig = {
-    name: "edge-config_delete-edge-config",
+    name: "edge-config-delete-edge-config",
     description: `Delete an Edge Config
 
 Delete an Edge Config by id.`,

package/esm/mcp-server/tools/edgeConfigDeleteEdgeConfigSchema.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteEdgeConfigSchemaRequest$inboundSchema,
 };
 export const tool$edgeConfigDeleteEdgeConfigSchema = {
-    name: "edge-config_delete-edge-config-schema",
+    name: "edge-config-delete-edge-config-schema",
     description: `Delete an Edge Config's schema
 
 Deletes the schema of existing Edge Config.`,

package/esm/mcp-server/tools/edgeConfigDeleteEdgeConfigTokens.js

@@ -8,7 +8,7 @@ const args = {
     request: DeleteEdgeConfigTokensRequest$inboundSchema,
 };
 export const tool$edgeConfigDeleteEdgeConfigTokens = {
-    name: "edge-config_delete-edge-config-tokens",
+    name: "edge-config-delete-edge-config-tokens",
     description: `Delete one or more Edge Config tokens
 
 Deletes one or more tokens of an existing Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfig.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfig = {
-    name: "edge-config_get-edge-config",
+    name: "edge-config-get-edge-config",
     description: `Get an Edge Config
 
 Returns an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigBackup.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigBackupRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigBackup = {
-    name: "edge-config_get-edge-config-backup",
+    name: "edge-config-get-edge-config-backup",
     description: `Get Edge Config backup
 
 Retrieves a specific version of an Edge Config from backup storage.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigBackups.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigBackupsRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigBackups = {
-    name: "edge-config_get-edge-config-backups",
+    name: "edge-config-get-edge-config-backups",
     description: `Get Edge Config backups
 
 Returns backups of an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigItem.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigItemRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigItem = {
-    name: "edge-config_get-edge-config-item",
+    name: "edge-config-get-edge-config-item",
     description: `Get an Edge Config item
 
 Returns a specific Edge Config Item.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigItems.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigItemsRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigItems = {
-    name: "edge-config_get-edge-config-items",
+    name: "edge-config-get-edge-config-items",
     description: `Get Edge Config items
 
 Returns all items of an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigSchema.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigSchemaRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigSchema = {
-    name: "edge-config_get-edge-config-schema",
+    name: "edge-config-get-edge-config-schema",
     description: `Get Edge Config schema
 
 Returns the schema of an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigToken.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigTokenRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigToken = {
-    name: "edge-config_get-edge-config-token",
+    name: "edge-config-get-edge-config-token",
     description: `Get Edge Config token meta data
 
 Return meta data about an Edge Config token.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigTokens.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigTokensRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigTokens = {
-    name: "edge-config_get-edge-config-tokens",
+    name: "edge-config-get-edge-config-tokens",
     description: `Get all tokens of an Edge Config
 
 Returns all tokens of an Edge Config.`,

package/esm/mcp-server/tools/edgeConfigGetEdgeConfigs.js

@@ -8,7 +8,7 @@ const args = {
     request: GetEdgeConfigsRequest$inboundSchema,
 };
 export const tool$edgeConfigGetEdgeConfigs = {
-    name: "edge-config_get-edge-configs",
+    name: "edge-config-get-edge-configs",
     description: `Get Edge Configs
 
 Returns all Edge Configs.`,

package/esm/mcp-server/tools/edgeConfigPatchEdgeConfigSchema.js

@@ -8,7 +8,7 @@ const args = {
     request: PatchEdgeConfigSchemaRequest$inboundSchema,
 };
 export const tool$edgeConfigPatchEdgeConfigSchema = {
-    name: "edge-config_patch-edge-config-schema",
+    name: "edge-config-patch-edge-config-schema",
     description: `Update Edge Config schema
 
 Update an Edge Config's schema.`,

package/esm/mcp-server/tools/edgeConfigUpdateEdgeConfig.js

@@ -8,7 +8,7 @@ const args = {
     request: UpdateEdgeConfigRequest$inboundSchema,
 };
 export const tool$edgeConfigUpdateEdgeConfig = {
-    name: "edge-config_update-edge-config",
+    name: "edge-config-update-edge-config",
     description: `Update an Edge Config
 
 Updates an Edge Config.`,

package/esm/mcp-server/tools/environmentCreateCustomEnvironment.js

@@ -8,7 +8,7 @@ const args = {
     request: CreateCustomEnvironmentRequest$inboundSchema,
 };
 export const tool$environmentCreateCustomEnvironment = {
-    name: "environment_create-custom-environment",
+    name: "environment-create-custom-environment",
     description: `Create a custom environment for the current project.
 
 Creates a custom environment for the current project. Cannot be named 'Production' or 'Preview'.`,