Skip to main content
Glama
andrewlwn77
by andrewlwn77

list_bases

Retrieve all available NocoDB projects and databases to manage tables, records, views, and file attachments for operational data storage.

Instructions

List all available NocoDB bases/projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_bases' MCP tool. It calls the NocoDB client's listBases method and formats the response with base details and count.
    handler: async (client: NocoDBClient) => {
      const bases = await client.listBases();
      return {
        bases: bases.map((base) => ({
          id: base.id,
          title: base.title,
          status: base.status,
          created_at: base.created_at,
          updated_at: base.updated_at,
        })),
        count: bases.length,
      };
    },
  • The input schema for the 'list_bases' tool, defining it as an empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • The 'list_bases' tool definition and registration within the databaseTools array.
    {
      name: "list_bases",
      description: "List all available NocoDB bases/projects",
      inputSchema: {
        type: "object",
        properties: {},
      },
      handler: async (client: NocoDBClient) => {
        const bases = await client.listBases();
        return {
          bases: bases.map((base) => ({
            id: base.id,
            title: base.title,
            status: base.status,
            created_at: base.created_at,
            updated_at: base.updated_at,
          })),
          count: bases.length,
        };
      },
    },
  • Helper method in NocoDBClient that performs the actual API call to list bases/projects from the NocoDB server.
    async listBases(): Promise<NocoDBBase[]> {
      const response = await this.client.get("/api/v1/db/meta/projects");
      return response.data.list;
    }
  • src/index.ts:55-62 (registration)
    Registration of databaseTools (including list_bases) into the combined allTools list used by the MCP server for tool handling.
    const allTools = [
      ...databaseTools,
      ...tableTools,
      ...recordTools,
      ...viewTools,
      ...queryTools,
      ...attachmentTools,
    ];
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. It states the action is to 'List all available' items, implying a read-only operation, but doesn't specify details like pagination, rate limits, error handling, or authentication requirements. For a tool with zero annotation coverage, this leaves significant behavioral aspects unclear.

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, clear sentence with no wasted words. It front-loads the key information ('List all available NocoDB bases/projects') efficiently, making it easy to parse. Every part of the sentence contributes directly to understanding the tool's purpose.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks context on usage, behavior, or output format. Without annotations or output schema, more detail on what 'list' entails (e.g., format, limitations) would improve completeness for agent invocation.

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 parameter details, which is appropriate here. A baseline of 4 is applied as it correctly avoids redundancy, though it doesn't enhance beyond the schema's completeness.

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 ('List') and the resource ('all available NocoDB bases/projects'), making the purpose evident. It doesn't explicitly differentiate from siblings like 'list_tables' or 'list_views', but the resource specificity (bases/projects) provides implicit distinction. However, it lacks explicit sibling comparison, preventing 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. It doesn't mention prerequisites, context, or exclusions, such as whether it requires authentication or if there are filtering options. With siblings like 'get_base_info' that might retrieve specific base details, the lack of comparative guidance is a notable gap.

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/andrewlwn77/nocodb-mcp'

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