Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_record

Retrieve a specific record by ID from a QuickBase table. Provide the table ID, record ID, and optional field IDs to fetch targeted data efficiently.

Instructions

Get a specific record by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldIdsNoSpecific field IDs to retrieve
recordIdYesRecord ID
tableIdYesTable ID

Implementation Reference

  • Core implementation of quickbase_get_record tool: Queries QuickBase records endpoint with where clause `{3.EX.${recordId}}` to fetch specific record by ID (field 3 is record ID), optionally selecting specific fields.
    async getRecord(tableId: string, recordId: number, fieldIds?: number[]): Promise<any> {
      const params: any = { from: tableId };
      if (fieldIds) {
        params.select = fieldIds;
      }
    
      const response = await this.axios.post('/records/query', {
        ...params,
        where: `{3.EX.${recordId}}`
      });
      
      return response.data.data[0] || null;
    }
  • src/index.ts:231-247 (registration)
    MCP server tool call handler registration in switch statement that validates args and delegates to QuickBaseClient.getRecord() method.
    case 'quickbase_get_record':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      const record = await this.qbClient.getRecord(
        args.tableId as string, 
        args.recordId as number, 
        args.fieldIds as number[]
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(record, null, 2),
          },
        ],
      };
  • Tool metadata and JSON input schema definition for quickbase_get_record, used for tool listing and validation.
    {
      name: 'quickbase_get_record',
      description: 'Get a specific record by ID',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          recordId: { type: 'number', description: 'Record ID' },
          fieldIds: { type: 'array', items: { type: 'number' }, description: 'Specific field IDs to retrieve' }
        },
        required: ['tableId', 'recordId']
      }
    },
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 this is a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error handling, or what happens if the record doesn't exist. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 extremely concise - a single sentence that communicates the core purpose without any wasted words. It's front-loaded with the essential information and earns its place efficiently.

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 read operation with no annotations and no output schema, the description is insufficient. It doesn't explain what format the returned record will be in, whether all fields are included by default, or how the optional 'fieldIds' parameter affects the response. Given the complexity of data retrieval and lack of structured metadata, more context is needed.

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 schema description coverage is 100%, with all parameters clearly documented in the input schema. The description doesn't add any additional meaning about the parameters beyond what's already in the schema, so it meets the baseline expectation but doesn't provide extra value.

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 ('Get') and resource ('a specific record by ID'), making the purpose immediately understandable. It distinguishes this from bulk operations like 'query_records' or 'search_records' by focusing on single-record retrieval, though it doesn't explicitly contrast with all siblings.

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 like 'quickbase_query_records' or 'quickbase_search_records'. It doesn't mention prerequisites, such as needing to know the exact record ID, or when other retrieval methods might be more appropriate.

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