Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_relationships

Retrieve and manage relationships for a specified table using the QuickBase MCP Server, enabling efficient data structure organization and integration.

Instructions

Get relationships for a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableIdYesTable ID

Implementation Reference

  • The main handler function that performs the QuickBase API GET request to /relationships?childTableId={tableId} and returns the response data.
    async getRelationships(tableId: string): Promise<any[]> {
      const response = await this.axios.get(`/relationships`, {
        params: { childTableId: tableId }
      });
      return response.data;
    }
  • Defines the tool's metadata including name, description, and input schema requiring a tableId.
    {
      name: 'quickbase_get_relationships',
      description: 'Get relationships for a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' }
        },
        required: ['tableId']
      }
    },
  • src/index.ts:351-362 (registration)
    Registers the tool in the MCP callTool handler switch case, validating args and calling the QuickBaseClient handler.
    case 'quickbase_get_relationships':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await this.qbClient.getRelationships(args.tableId as string), null, 2),
          },
        ],
      };
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 only states the action ('Get') without details on permissions, rate limits, output format, or whether it's a read-only operation. For a tool with no annotations, this is insufficient to inform the agent about how the tool behaves beyond its basic purpose.

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, straightforward sentence that efficiently conveys the tool's purpose without unnecessary words. It is front-loaded and to the point, though it could be slightly more informative 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 lack of annotations and output schema, the description is incomplete. It does not explain what 'relationships' entail, the format of the output, or any behavioral aspects like error handling. For a tool with no structured data beyond the input schema, more context is needed to guide effective use by an AI agent.

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' documented as 'Table ID'. The description does not add any additional meaning or context beyond this, such as explaining what a table ID is or where to find it. Given the high schema coverage, a baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 'Get relationships for a table' clearly states the action (get) and resource (relationships for a table), which is adequate. However, it lacks specificity about what 'relationships' means in this context (e.g., foreign keys, joins, or metadata) and does not distinguish it from sibling tools like 'quickbase_get_relationship_details' or 'quickbase_validate_relationship', making it vague in 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. There are multiple sibling tools related to relationships (e.g., 'quickbase_get_relationship_details', 'quickbase_validate_relationship'), but no indication of how this tool differs or when it is preferred. This leaves the agent without context for selection.

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