Skip to main content
Glama
datastax

Astra DB MCP Server

Official

UpdateCollection

Modify an existing collection in Astra DB by renaming it using the specified new name. Simplifies database management through direct updates.

Instructions

Update an existing collection in the database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionNameYesName of the collection to update
newNameYesNew name for the collection

Implementation Reference

  • The core handler function that renames a collection by creating a new one with the same data and vector settings, copying documents, and dropping the old collection.
    export async function UpdateCollection(params: {
      collectionName: string;
      newName: string;
    }) {
      const { collectionName, newName } = params;
    
      // Check if source collection exists
      const collections = await db.listCollections();
      const sourceCollectionExists = collections.some(
        (collection) => collection.name === collectionName
      );
    
      if (!sourceCollectionExists) {
        throw new Error(`Collection '${collectionName}' does not exist`);
      }
    
      // Check if target collection already exists
      const targetCollectionExists = collections.some(
        (collection) => collection.name === newName
      );
    
      if (targetCollectionExists) {
        throw new Error(`Collection '${newName}' already exists`);
      }
    
      // Create new collection
      const sourceCollection = db.collection(collectionName);
      // Get the source collection info to preserve settings
      const collectionInfo = await sourceCollection.find({}).limit(1).toArray();
      const hasVectors =
        collectionInfo.length > 0 && collectionInfo[0].$vector !== undefined;
    
      // Create the new collection with the same settings
      if (hasVectors) {
        const vectorDimension = collectionInfo[0].$vector.length;
        await db.createCollection(newName, {
          vector: {
            dimension: vectorDimension,
          },
        });
      } else {
        await db.createCollection(newName);
      }
    
      // Copy data
      const targetCollection = db.collection(newName);
      const documents = await sourceCollection.find({}).toArray();
    
      if (documents.length > 0) {
        await targetCollection.insertMany(documents);
      }
    
      // Delete the old collection
      await db.dropCollection(collectionName);
    
      return {
        success: true,
        message: `Collection '${collectionName}' renamed to '${newName}' successfully`,
      };
    }
  • The tool schema definition including name, description, and input validation schema for UpdateCollection.
    {
      name: "UpdateCollection",
      description: "Update an existing collection in the database",
      inputSchema: {
        type: "object",
        properties: {
          collectionName: {
            type: "string",
            description: "Name of the collection to update",
          },
          newName: {
            type: "string",
            description: "New name for the collection",
          },
        },
        required: ["collectionName", "newName"],
      },
    },
  • index.ts:113-125 (registration)
    The dispatch case in the CallToolRequest handler that invokes the UpdateCollection function.
    case "UpdateCollection":
      const updateResult = await UpdateCollection({
        collectionName: args.collectionName as string,
        newName: args.newName as string,
      });
      return {
        content: [
          {
            type: "text",
            text: updateResult.message,
          },
        ],
      };
  • index.ts:61-65 (registration)
    Registration of the listTools capability which includes UpdateCollection via the imported tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation, it doesn't specify required permissions, whether the operation is idempotent, error conditions (e.g., if the collection doesn't exist), or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan and understand quickly.

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?

Given that this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, errors), usage context, and return values, which are critical for an AI agent to invoke it correctly.

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?

The schema description coverage is 100%, with both parameters (collectionName and newName) clearly documented in the schema. The description doesn't add any additional meaning beyond what the schema provides, such as format constraints or examples, so it meets the baseline for high schema coverage.

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 ('Update') and resource ('an existing collection in the database'), which is specific and unambiguous. However, it doesn't distinguish this tool from sibling tools like UpdateRecord or BulkUpdateRecords, which also perform updates on different resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that the collection must exist), exclusions, or comparisons to siblings like UpdateRecord (for individual records) or BulkUpdateRecords (for batch operations).

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

Related 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/datastax/astra-db-mcp'

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