Skip to main content
Glama
andrewlwn77
by andrewlwn77

list_tables

Retrieve all tables within a specified NocoDB base to view database structure and available data collections.

Instructions

List all tables in a base

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project

Implementation Reference

  • The handler function for the 'list_tables' MCP tool. It calls the NocoDB client's listTables method with the provided base_id and returns a formatted response containing the list of tables with selected metadata fields and the total count.
    handler: async (client: NocoDBClient, args: { base_id: string }) => {
      const tables = await client.listTables(args.base_id);
      return {
        tables: tables.map((table) => ({
          id: table.id,
          table_name: table.table_name,
          title: table.title,
          type: table.type,
          enabled: table.enabled,
          created_at: table.created_at,
          updated_at: table.updated_at,
        })),
        count: tables.length,
      };
    },
  • The input schema definition for the 'list_tables' tool, specifying an object with a required 'base_id' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "The ID of the base/project",
        },
      },
      required: ["base_id"],
    },
  • src/index.ts:55-62 (registration)
    Combines and registers 'tableTools' (which includes 'list_tables') with other tool sets into 'allTools', which is used by the MCP server to handle ListToolsRequestSchema and CallToolRequestSchema.
    const allTools = [
      ...databaseTools,
      ...tableTools,
      ...recordTools,
      ...viewTools,
      ...queryTools,
      ...attachmentTools,
    ];
  • Helper method in NocoDBClient that performs the actual API call to retrieve the list of tables for a given base ID via the NocoDB meta endpoint.
    async listTables(baseId: string): Promise<NocoDBTable[]> {
      const response = await this.client.get(
        `/api/v1/db/meta/projects/${baseId}/tables`,
      );
      return response.data.list;
    }
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 action but does not cover important traits like whether it's read-only, pagination behavior, error handling, or output format, leaving significant gaps for an agent.

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, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete. It fails to address behavioral aspects like safety, response format, or error conditions, which are crucial for an agent to use the tool effectively in this context.

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 input schema has 100% description coverage, so the parameter 'base_id' is well-documented in the schema. The description adds no additional meaning beyond implying the tool operates within a base, which aligns with the schema but doesn't enhance parameter understanding.

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 resource ('tables in a base'), making the purpose understandable. However, it does not differentiate from sibling tools like 'list_bases' or 'list_views', which also list resources, so it lacks explicit distinction.

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, such as 'list_bases' for bases or 'get_table_info' for specific table details. It also omits prerequisites like needing a valid base_id, leaving usage context unclear.

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