Skip to main content
Glama
datastax

Astra DB MCP Server

Official

GetCollections

Retrieve all collections stored in the Astra DB database using the MCP Server, enabling efficient database management and interaction through natural language commands.

Instructions

Get all collections in the Astra DB database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that executes the tool logic: lists all collections from the Astra DB using db.listCollections() and returns them.
    export async function GetCollections() {
      const collections = await db.listCollections();
      return collections;
    }
  • The schema definition for the GetCollections tool, specifying no input parameters.
    {
      name: "GetCollections",
      description: "Get all collections in the Astra DB database",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • index.ts:61-65 (registration)
    Registration of the ListTools handler which exposes the tools list (including GetCollections schema).
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
  • index.ts:73-82 (registration)
    The dispatch case in CallToolRequestSchema handler that calls the GetCollections handler and returns formatted response.
    case "GetCollections":
      const collections = await GetCollections();
      return {
        content: [
          {
            type: "text",
            text: collections.map((c) => c.name).join("\n"),
          },
        ],
      };
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves collections but doesn't specify whether this is a read-only operation, if it requires authentication, what format the results are in, or any rate limits. This leaves significant gaps for an agent to understand how to use it effectively.

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 that directly states the tool's purpose without any unnecessary words or fluff. It is perfectly front-loaded and wastes no space.

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 the complexity of a database query tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'collections' are in this context, the return format, or any behavioral aspects like pagination or error handling, leaving the agent with incomplete information.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, which is correct for this case, earning a high baseline score.

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 ('Get all collections') and resource ('in the Astra DB database'), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'ListRecords' or 'EstimateDocumentCount' that might also retrieve collection-related information, so it falls short of a perfect score.

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 like 'ListRecords' or 'EstimateDocumentCount', nor does it mention prerequisites or exclusions. It merely states what the tool does without contextual usage information.

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