Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_query_records

Retrieve and filter records from a QuickBase table using specific criteria, select fields, and apply sorting for efficient data management. Simplify querying with customizable options.

Instructions

Query records from a table with optional filtering and sorting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectNoField IDs to select
skipNoNumber of records to skip
sortByNoSort criteria
tableIdYesTable ID to query
topNoMax number of records
whereNoQuickBase query filter (e.g., "{6.EX.'John'}")

Implementation Reference

  • Core implementation of the quickbase_query_records tool. Constructs query parameters from options and calls QuickBase /records/query API endpoint.
    async getRecords(tableId: string, options?: QueryOptions): Promise<any[]> {
      const params: any = { from: tableId };
      
      if (options?.select) {
        params.select = options.select;
      }
      if (options?.where) {
        params.where = options.where;
      }
      if (options?.sortBy) {
        params.sortBy = options.sortBy;
      }
      if (options?.groupBy) {
        params.groupBy = options.groupBy;
      }
      if (options?.top) {
        params.top = options.top;
      }
      if (options?.skip) {
        params.skip = options.skip;
      }
    
      const response = await this.axios.post('/records/query', params);
      return response.data.data;
    }
  • src/index.ts:211-229 (registration)
    MCP server dispatch handler for quickbase_query_records tool call, validates args and invokes QuickBaseClient.getRecords.
    case 'quickbase_query_records':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      const records = await this.qbClient.getRecords(args.tableId as string, {
        select: args.select as number[],
        where: args.where as string,
        sortBy: args.sortBy as any[],
        top: args.top as number,
        skip: args.skip as number
      });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(records, null, 2),
          },
        ],
      };
  • Tool definition and JSON input schema for quickbase_query_records, used for MCP tool listing and validation.
      name: 'quickbase_query_records',
      description: 'Query records from a table with optional filtering and sorting',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID to query' },
          select: { type: 'array', items: { type: 'number' }, description: 'Field IDs to select' },
          where: { type: 'string', description: 'QuickBase query filter (e.g., "{6.EX.\'John\'}")' },
          sortBy: { 
            type: 'array', 
            items: {
              type: 'object',
              properties: {
                fieldId: { type: 'number' },
                order: { type: 'string', enum: ['ASC', 'DESC'] }
              }
            },
            description: 'Sort criteria'
          },
          top: { type: 'number', description: 'Max number of records' },
          skip: { type: 'number', description: 'Number of records to skip' }
        },
        required: ['tableId']
      }
    },
  • Zod schema for input validation of quickbase_query_records parameters (QueryRecordsSchema).
    const QueryRecordsSchema = z.object({
      tableId: z.string().describe('Table ID to query'),
      select: z.array(z.number()).optional().describe('Field IDs to select'),
      where: z.string().optional().describe('QuickBase query filter'),
      sortBy: z.array(z.object({
        fieldId: z.number(),
        order: z.enum(['ASC', 'DESC']).default('ASC')
      })).optional().describe('Sort criteria'),
      top: z.number().optional().describe('Max number of records'),
      skip: z.number().optional().describe('Number of records to skip')
    });
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 for behavioral disclosure. It mentions 'optional filtering and sorting' but fails to describe critical behaviors like pagination handling (implied by skip/top), error conditions, authentication needs, rate limits, or what the output looks like (no output schema). This is inadequate for a query tool with multiple parameters.

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 front-loads the core purpose ('query records from a table') and adds key modifiers ('with optional filtering and sorting'). There's no wasted text, making it highly concise and well-structured.

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?

For a query tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects like pagination, error handling, and output format, which are crucial for an AI agent to use this tool effectively. The high schema coverage doesn't compensate for these gaps in behavioral 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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning 'optional filtering and sorting,' which aligns with the 'where' and 'sortBy' parameters but doesn't provide additional context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('query') and resource ('records from a table'), making the purpose evident. However, it doesn't distinguish this tool from sibling tools like 'quickbase_search_records' or 'quickbase_run_report', which likely have overlapping functionality for retrieving records.

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. With siblings like 'quickbase_search_records' and 'quickbase_run_report' available, there's no indication of which scenarios favor this query tool over those options, leaving usage 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

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