Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_create_table

Create a custom table in QuickBase by specifying a name and description using this tool. It enables structured data management within applications hosted on the QuickBase MCP Server.

Instructions

Create a new table in QuickBase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoTable description
nameYesTable name

Implementation Reference

  • Core handler function that executes the QuickBase API call to create a new table.
    async createTable(table: { name: string; description?: string }): Promise<string> {
      const response = await this.axios.post('/tables', {
        appId: this.config.appId,
        name: table.name,
        description: table.description,
        singleRecordName: table.name.slice(0, -1), // Remove 's' for singular
        pluralRecordName: table.name
      });
      return response.data.id;
    }
  • MCP server handler that processes the tool call and delegates to QuickBaseClient.createTable.
    case 'quickbase_create_table':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      const tableId = await this.qbClient.createTable({
        name: args.name as string,
        description: args.description as string
      });
      return {
        content: [
          {
            type: 'text',
            text: `Table created with ID: ${tableId}`,
          },
        ],
      };
  • Tool registration in the quickbaseTools array, including name, description, and input schema.
      name: 'quickbase_create_table',
      description: 'Create a new table in QuickBase',
      inputSchema: {
        type: 'object',
        properties: {
          name: { type: 'string', description: 'Table name' },
          description: { type: 'string', description: 'Table description' }
        },
        required: ['name']
      }
    },
  • Zod schema for validating create table input parameters.
    const CreateTableSchema = z.object({
      name: z.string().describe('Table name'),
      description: z.string().optional().describe('Table description')
    });
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 'Create' implies a mutation, but lacks details on permissions required, whether the operation is reversible, what happens on failure, or typical response formats. This is inadequate for a mutation tool with zero annotation coverage.

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 unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 creating a table (a mutation with potential side effects), no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like error handling, return values, or how it differs from sibling table-creation tools, leaving significant gaps for an agent.

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?

Schema description coverage is 100%, with both parameters ('name' and 'description') documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as naming constraints or usage examples, so it meets the baseline for high schema coverage.

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 ('Create') and resource ('new table in QuickBase'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'quickbase_create_junction_table' or 'quickbase_create_relationship', which also create tables but with specific configurations.

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 app context), exclusions, or comparisons to sibling tools like 'quickbase_create_junction_table' for specialized table types, leaving the agent to infer usage from tool names alone.

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