Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_update_field

Modify field properties in QuickBase tables by updating labels, requirements, or choices. Specify table and field IDs to ensure precise adjustments for improved data management.

Instructions

Update an existing field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
choicesNoNew choices for choice fields
fieldIdYesField ID to update
labelNoNew field label
requiredNoWhether field is required
tableIdYesTable ID

Implementation Reference

  • Core implementation of the quickbase_update_field tool: sends a POST request to QuickBase API /fields/{fieldId} with tableId and field updates.
    async updateField(tableId: string, fieldId: number, updates: Partial<QuickBaseField>): Promise<void> {
      await this.axios.post(`/fields/${fieldId}`, {
        tableId,
        ...updates
      });
    }
  • Input schema definition for the quickbase_update_field tool, defining parameters like tableId, fieldId, label, required, choices.
    {
      name: 'quickbase_update_field',
      description: 'Update an existing field',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' },
          fieldId: { type: 'number', description: 'Field ID to update' },
          label: { type: 'string', description: 'New field label' },
          required: { type: 'boolean', description: 'Whether field is required' },
          choices: { type: 'array', items: { type: 'string' }, description: 'New choices for choice fields' }
        },
        required: ['tableId', 'fieldId']
      }
    },
  • src/index.ts:178-194 (registration)
    MCP server handler registration: switch case that parses args and calls qbClient.updateField, returns success message.
    case 'quickbase_update_field':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      await this.qbClient.updateField(args.tableId as string, args.fieldId as number, {
        label: args.label as string,
        required: args.required as boolean,
        choices: args.choices as string[]
      });
      return {
        content: [
          {
            type: 'text',
            text: `Field ${args.fieldId} updated successfully`,
          },
        ],
      };
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 'Update an existing field,' which implies a mutation operation, but it doesn't disclose behavioral traits such as permissions required, whether updates are reversible, rate limits, or what happens if the field doesn't exist. This is a significant gap for a mutation tool with zero annotation coverage.

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 extremely concise with a single sentence, 'Update an existing field,' which is front-loaded and wastes no words. Every part of it is essential, making it efficient and easy to parse.

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 updating a field in a database system, no annotations, and no output schema, the description is incomplete. It doesn't explain what gets updated (e.g., properties like label or required), potential side effects, or return values. For a mutation tool with 5 parameters, this leaves too many gaps 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%, so the schema already documents all 5 parameters (choices, fieldId, label, required, tableId). The description doesn't add any meaning beyond what the schema provides, such as explaining how choices work for choice fields or the impact of setting required. Baseline 3 is appropriate when 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 'Update an existing field' clearly states the verb ('update') and resource ('field'), but it's vague about what specifically gets updated. It doesn't distinguish this tool from sibling tools like 'quickbase_update_record' or 'quickbase_create_field', which also involve field operations. The purpose is understandable but lacks specificity.

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. With siblings like 'quickbase_update_record' (for updating records) and 'quickbase_create_field' (for creating fields), the description doesn't clarify that this is specifically for modifying field properties, not records or new fields. There's no mention of prerequisites or exclusions.

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