Skip to main content
Glama
datastax

Astra DB MCP Server

Official

HelpAddToClient

Integrate Astra DB client into your MCP client to enable database interactions through natural language commands, streamlining collection and record management.

Instructions

Help the user add the Astra DB client to their MCP client

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the HelpAddToClient tool. It fetches the contents of the project's README.md from GitHub and returns it wrapped in a success object with an 'instructions' field.
    export async function HelpAddToClient() {
      const instructions = await fetch(
        "https://raw.githubusercontent.com/datastax/astra-db-mcp/refs/heads/main/README.md"
      ).then((res) => res.text());
    
      return {
        success: true,
        instructions,
      };
    }
  • tools.ts:453-461 (registration)
    The registration of the HelpAddToClient tool in the exported 'tools' array, including its name, description, and empty input schema (no parameters required).
    {
      name: "HelpAddToClient",
      description: "Help the user add the Astra DB client to their MCP client",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • TypeScript type definition for ToolName union that includes "HelpAddToClient" among other tool names, used for type safety in tool handling.
    export type ToolName =
      | "GetCollections"
      | "CreateCollection"
      | "UpdateCollection"
      | "DeleteCollection"
      | "ListRecords"
      | "GetRecord"
      | "CreateRecord"
      | "UpdateRecord"
      | "DeleteRecord"
      | "FindRecord"
      | "FindDistinctValues"
      | "BulkCreateRecords"
      | "BulkUpdateRecords"
      | "BulkDeleteRecords"
      | "OpenBrowser"
      | "HelpAddToClient"
      | "EstimateDocumentCount"
      | "VectorSearch"
      | "HybridSearch";
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'add' but doesn't disclose behavioral traits such as whether this requires user interaction, modifies system files, needs authentication, or has side effects. For a setup tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness4/5

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

The description is a single, clear sentence that efficiently states the tool's purpose without fluff. It's front-loaded and easy to parse, though it could be slightly more specific (e.g., 'configure' vs. 'add') to improve precision without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (setup-related, no params, no output schema), the description is minimally adequate. It states what the tool does but lacks details on behavior, prerequisites, or outcomes. Without annotations or output schema, it should provide more context (e.g., what 'add' entails, expected result) to be fully complete.

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 doesn't add param info, which is appropriate, but it could hint at implicit inputs (e.g., user context). Baseline is 4 for zero params, as it avoids unnecessary detail.

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 ('add') and resource ('Astra DB client to their MCP client'), making the purpose understandable. It distinguishes from siblings like BulkCreateRecords or OpenBrowser by focusing on client setup rather than data operations. However, it doesn't specify what 'add' entails (e.g., installation, configuration, authentication), keeping it from 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 implies usage when the user needs to set up the Astra DB client, but provides no explicit guidance on when to use this tool versus alternatives or prerequisites. With siblings like OpenBrowser that might handle web-based setup, there's no comparison or exclusion criteria mentioned.

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