Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_table_fields

Retrieve all fields for a specified table using the QuickBase MCP Server, enabling efficient management and organization of table structures.

Instructions

Get all fields for a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableIdYesQuickBase table ID

Implementation Reference

  • The core handler function that executes the tool logic by making an API request to QuickBase to retrieve all fields for the given table ID.
    async getTableFields(tableId: string): Promise<any[]> {
      const response = await this.axios.get(`/fields`, {
        params: { tableId }
      });
      return response.data;
    }
  • Defines the tool's metadata including name, description, and input schema validation (requiring tableId string).
    {
      name: 'quickbase_get_table_fields',
      description: 'Get all fields for a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'QuickBase table ID' }
        },
        required: ['tableId']
      }
    },
  • src/index.ts:140-151 (registration)
    Registers the tool handler in the MCP server's switch statement, dispatching calls to the QuickBaseClient.getTableFields method.
    case 'quickbase_get_table_fields':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await this.qbClient.getTableFields(args.tableId as string), null, 2),
          },
        ],
      };
  • src/index.ts:49-54 (registration)
    Registers the list tools handler which returns the quickbaseTools array containing this tool's schema.
    // List available tools
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: quickbaseTools,
      };
    });
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 'Get all fields for a table', which implies a read-only operation, but does not specify aspects like authentication requirements, rate limits, pagination, error handling, or what 'all fields' entails (e.g., field types, permissions). This leaves significant gaps in understanding the tool's 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 a single, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy for an agent 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 lack of annotations and output schema, the description is incomplete for a tool that retrieves metadata. It does not explain what 'fields' include (e.g., names, IDs, types) or the return format, leaving the agent uncertain about the result. For a read operation with no structured output documentation, more detail is needed to be fully helpful.

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 description does not add any parameter-specific information beyond what the input schema provides. With 100% schema description coverage (the 'tableId' parameter is fully documented in the schema), the baseline score is 3. The description does not compensate with additional context, such as how to obtain the table ID or format requirements.

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 'Get all fields for a table' clearly states the verb ('Get') and resource ('fields for a table'), making the purpose immediately understandable. However, it does not distinguish this tool from potential alternatives like 'quickbase_get_table_info' or 'quickbase_get_relationships', which might also retrieve table-related metadata, so it lacks sibling differentiation.

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_get_table_info' and 'quickbase_get_relationships' that might overlap in functionality, there is no explicit or implied context for choosing this specific tool, leaving the agent without usage direction.

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