Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_table_info

Retrieve detailed metadata about a specific table in QuickBase by providing its table ID. This tool helps users manage and analyze table structures efficiently.

Instructions

Get detailed information about a specific table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableIdYesQuickBase table ID

Implementation Reference

  • Implements the core logic for retrieving detailed information about a specific QuickBase table using the QuickBase API.
    async getTableInfo(tableId: string): Promise<any> {
      const response = await this.axios.get(`/tables/${tableId}`, {
        params: { appId: this.config.appId }
      });
      return response.data;
    }
  • src/index.ts:112-123 (registration)
    Registers the tool handler in the MCP server switch statement within CallToolRequestSchema handler, extracting tableId argument, calling qbClient.getTableInfo, and returning formatted JSON response.
    case 'quickbase_get_table_info':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await this.qbClient.getTableInfo(args.tableId as string), null, 2),
          },
        ],
      };
  • Defines the MCP Tool object with name, description, and inputSchema for 'quickbase_get_table_info', used in quickbaseTools array for listTools response.
    {
      name: 'quickbase_get_table_info',
      description: 'Get detailed information about a specific table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'QuickBase table ID' }
        },
        required: ['tableId']
      }
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose if this is a read-only operation, requires specific permissions, has rate limits, or what the output format might be. 'Get detailed information' implies a safe read, but this isn't explicitly stated, leaving gaps for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action, though it could be slightly more specific (e.g., 'Get metadata like name, fields, and permissions for a table') to improve clarity without losing conciseness.

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 a tool that retrieves 'detailed information' about a database table, with no annotations and no output schema, the description is incomplete. It doesn't hint at what information is returned (e.g., schema, permissions, metadata), making it hard for an agent to understand the tool's full context and use it effectively.

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 input schema has 100% description coverage, with the single parameter 'tableId' clearly documented. The description adds no additional meaning beyond the schema, such as examples or context for obtaining the table ID. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb ('Get') and resource ('detailed information about a specific table'), which is clear but vague. It doesn't specify what 'detailed information' includes or distinguish this tool from siblings like 'quickbase_get_tables' (which likely lists tables) or 'quickbase_get_table_fields' (which focuses on fields).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used for metadata retrieval before other operations or how it differs from 'quickbase_get_tables' or 'quickbase_get_app_info'. The description only states what it does, not when to choose it.

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