Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_relationship_details

Retrieve comprehensive details about table relationships and lookup fields for a specified table ID, including optional related field information, using the QuickBase MCP Server.

Instructions

Get detailed information about table relationships including lookup fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeFieldsNoInclude related field details
tableIdYesTable ID to analyze relationships for

Implementation Reference

  • Core handler function that retrieves detailed relationship information for a specified table, including parent/child relationships and optionally related reference/lookup fields.
    async getRelationshipDetails(tableId: string, includeFields: boolean = true): Promise<any> {
      try {
        const relationships = await this.getRelationships(tableId);
        const tableInfo = await this.getTableInfo(tableId);
        
        const result = {
          tableId,
          tableName: tableInfo.name,
          relationships: [] as any[],
          relatedFields: [] as any[]
        };
    
        for (const relationship of relationships) {
          const relationshipDetail: any = {
            parentTableId: relationship.parentTableId,
            childTableId: relationship.childTableId,
            foreignKeyFieldId: relationship.foreignKeyFieldId,
            type: 'one-to-many' // QuickBase primarily supports one-to-many
          };
    
          if (includeFields) {
            // Get fields related to this relationship
            const fields = await this.getTableFields(tableId);
            const relatedFields = fields.filter(field => 
              field.fieldType === 'reference' || 
              field.fieldType === 'lookup' ||
              (field.properties && field.properties.lookupReference)
            );
            
            relationshipDetail.relatedFields = relatedFields;
          }
    
          result.relationships.push(relationshipDetail);
        }
    
        return result;
      } catch (error) {
        console.error('Error getting relationship details:', error);
        throw error;
      }
    }
  • Tool registration entry defining the tool name, description, and input schema for MCP integration.
    {
      name: 'quickbase_get_relationship_details',
      description: 'Get detailed information about table relationships including lookup fields',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID to analyze relationships for' },
          includeFields: { type: 'boolean', default: true, description: 'Include related field details' }
        },
        required: ['tableId']
      }
    },
  • JSON schema defining the input parameters for the tool.
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID to analyze relationships for' },
          includeFields: { type: 'boolean', default: true, description: 'Include related field details' }
        },
        required: ['tableId']
      }
    },
  • Helper method to fetch basic relationships for a table, used within getRelationshipDetails.
    async getRelationships(tableId: string): Promise<any[]> {
      const response = await this.axios.get(`/relationships`, {
        params: { childTableId: tableId }
      });
      return response.data;
    }
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. While it indicates this is a read operation ('Get'), it doesn't mention authentication requirements, rate limits, error conditions, or what format the detailed information will be returned in. For a tool with no annotation coverage, this leaves significant gaps.

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 immediately communicates the core functionality. There's no wasted verbiage or unnecessary elaboration, making it easy to parse and understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with good schema coverage but no output schema or annotations, the description is minimally adequate. It states what the tool does but lacks important context about return format, error handling, and differentiation from sibling tools. The absence of an output schema means the description should ideally provide more information about what 'detailed information' includes.

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 fully documents both parameters. The description doesn't add any additional meaning about the parameters beyond what's in the schema descriptions. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 ('Get detailed information') and resource ('table relationships including lookup fields'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'quickbase_get_relationships' or 'quickbase_get_table_fields', which likely provide overlapping functionality.

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 sibling tools like 'quickbase_get_relationships' and 'quickbase_get_table_fields' available, there's no indication of how this tool differs in scope or when it's the appropriate choice.

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