Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_create_relationship

Establish parent-child relationships between tables by linking them via a foreign key field using this MCP server tool for QuickBase.

Instructions

Create a parent-child relationship between tables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
childTableIdYesChild table ID
foreignKeyFieldIdYesForeign key field ID in child table
parentTableIdYesParent table ID

Implementation Reference

  • Core implementation of quickbase_create_relationship: sends POST request to QuickBase /relationships endpoint with parent/child table IDs and foreign key field ID.
    async createRelationship(parentTableId: string, childTableId: string, foreignKeyFieldId: number): Promise<void> {
      await this.axios.post('/relationships', {
        parentTableId,
        childTableId,
        foreignKeyFieldId
      });
    }
  • MCP server handler for the tool call: validates args, calls QuickBaseClient.createRelationship, and returns success message.
    case 'quickbase_create_relationship':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.createRelationship(
        args.parentTableId as string,
        args.childTableId as string,
        args.foreignKeyFieldId as number
      );
      return {
        content: [
          {
            type: 'text',
            text: `Relationship created between ${args.parentTableId} and ${args.childTableId}`,
          },
        ],
      };
  • Zod input schema definition for validating tool parameters.
    const CreateRelationshipSchema = z.object({
      parentTableId: z.string().describe('Parent table ID'),
      childTableId: z.string().describe('Child table ID'),
      foreignKeyFieldId: z.number().describe('Foreign key field ID in child table')
    });
  • Tool registration in quickbaseTools array, including name, description, and input schema for MCP discovery.
    {
      name: 'quickbase_create_relationship',
      description: 'Create a parent-child relationship between tables',
      inputSchema: {
        type: 'object',
        properties: {
          parentTableId: { type: 'string', description: 'Parent table ID' },
          childTableId: { type: 'string', description: 'Child table ID' },
          foreignKeyFieldId: { type: 'number', description: 'Foreign key field ID in child table' }
        },
        required: ['parentTableId', 'childTableId', 'foreignKeyFieldId']
      }
    },
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. It states the action ('create') but doesn't disclose behavioral traits such as permissions required, whether the operation is reversible/destructive, error conditions, or what happens to existing data. This is a significant gap for a mutation tool.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and every word earns its place, making it easy 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks context on behavioral aspects (e.g., side effects, permissions), usage guidelines, and output details. Given the complexity of creating database relationships, more information is needed for effective use.

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%, with clear parameter descriptions in the schema (e.g., 'Child table ID'). The description adds no additional meaning beyond the schema, such as explaining the relationship between parameters or providing examples. 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.

Purpose4/5

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

The description clearly states the verb ('create') and resource ('parent-child relationship between tables'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'quickbase_create_advanced_relationship' or 'quickbase_create_lookup_field', which likely handle related but distinct operations.

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. It doesn't mention prerequisites (e.g., existing tables/fields), when to choose this over 'quickbase_create_advanced_relationship', or any exclusions (e.g., cannot create relationships between certain table types).

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