Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_tables

Retrieve a comprehensive list of all tables within a QuickBase application using this MCP server tool, enabling efficient data management and organization.

Instructions

Get list of all tables in the application

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the QuickBase API request to get all tables in the application.
    async getAppTables(): Promise<any[]> {
      const response = await this.axios.get(`/tables`, {
        params: { appId: this.config.appId }
      });
      return response.data;
    }
  • MCP server dispatch handler that calls the client method for quickbase_get_tables tool.
    case 'quickbase_get_tables':
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await this.qbClient.getAppTables(), null, 2),
          },
        ],
      };
  • Tool schema definition including name, description, and empty input schema (no parameters required).
      name: 'quickbase_get_tables',
      description: 'Get list of all tables in the application',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
  • src/index.ts:50-52 (registration)
    Registration of all tools including quickbase_get_tables via the quickbaseTools export.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: quickbaseTools,
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 but offers minimal insight. It implies a read-only operation ('Get list') but doesn't specify aspects like authentication requirements, rate limits, pagination, error handling, or the format of the returned list (e.g., array of table names or objects).

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 zero wasted words. It's front-loaded with the core purpose ('Get list of all tables'), making it highly efficient and easy to parse at a glance.

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 for a tool that likely returns structured data. It doesn't explain what the output contains (e.g., table IDs, names, metadata), how results are formatted, or any limitations (e.g., max tables returned). This leaves significant gaps for an AI agent to use it effectively.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description doesn't mislead about inputs.

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 list') and resource ('all tables in the application'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'quickbase_get_table_info' or 'quickbase_get_table_fields', which also retrieve table-related information but with different scopes.

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., needing an application context), exclusions, or comparisons to siblings like 'quickbase_get_table_info' for detailed metadata or 'quickbase_get_table_fields' for field-level data.

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/LawrenceCirillo/QuickBase-MCP-Server'

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