Skip to main content
Glama
novitalabs

Novita MCP Server

Official
by novitalabs

update-network-storage

Modify network storage capacity and rename storage volumes on the Novita AI platform to accommodate growing data needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
storageIdYesThe unique ID of the network storage to update. Please ensure it exists before updating.
storageNameNoNew name for the network storage. This is optional, if not provided, the name will not be changed. Use only letters, numbers, and hyphens
storageSizeYesNew size in GB (must be larger than current size). You can use the `list-network-storage` tool to get the current size if you don't know it.

Implementation Reference

  • Handler function for the 'update-network-storage' tool. It sends a POST request to the /networkstorage/update endpoint with the provided parameters and returns the JSON response as text content.
    }, async (params) => {
        const result = await novitaRequest(`/networkstorage/update`, "POST", params);
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(result, null, 2),
                },
            ],
        };
    });
  • Input schema using Zod for validating parameters: storageId (required string), storageName (optional string), storageSize (required number >=10).
    storageId: z
        .string()
        .nonempty()
        .describe("The unique ID of the network storage to update. Please ensure it exists before updating."),
    storageName: z
        .string()
        .optional()
        .describe("New name for the network storage. This is optional, if not provided, the name will not be changed. Use only letters, numbers, and hyphens"),
    storageSize: z
        .number()
        .min(10)
        .describe("New size in GB (must be larger than current size). You can use the `list-network-storage` tool to get the current size if you don't know it."),
  • src/tools.ts:574-597 (registration)
    Registration of the 'update-network-storage' tool on the MCP server, including input schema and handler.
    server.tool("update-network-storage", {
        storageId: z
            .string()
            .nonempty()
            .describe("The unique ID of the network storage to update. Please ensure it exists before updating."),
        storageName: z
            .string()
            .optional()
            .describe("New name for the network storage. This is optional, if not provided, the name will not be changed. Use only letters, numbers, and hyphens"),
        storageSize: z
            .number()
            .min(10)
            .describe("New size in GB (must be larger than current size). You can use the `list-network-storage` tool to get the current size if you don't know it."),
    }, async (params) => {
        const result = await novitaRequest(`/networkstorage/update`, "POST", params);
        return {
            content: [
                {
                    type: "text",
                    text: JSON.stringify(result, null, 2),
                },
            ],
        };
    });
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/novitalabs/novita-mcp-server'

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