Skip to main content
Glama
andrewlwn77
by andrewlwn77

insert_record

Add a new record to a NocoDB table by specifying the base ID, table name, and data to insert.

Instructions

Insert a single record into a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project
table_nameYesThe name of the table
dataYesThe record data to insert

Implementation Reference

  • Handler function for the 'insert_record' MCP tool. Receives NocoDBClient and input arguments, calls client.createRecord to insert the record into the specified table, and returns the created record with a success message.
    handler: async (
      client: NocoDBClient,
      args: {
        base_id: string;
        table_name: string;
        data: any;
      },
    ) => {
      const record = await client.createRecord(
        args.base_id,
        args.table_name,
        args.data,
      );
      return {
        record,
        message: "Record inserted successfully",
      };
    },
  • Input schema for the 'insert_record' tool, defining properties for base_id (string), table_name (string), and data (object), all required.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "The ID of the base/project",
        },
        table_name: {
          type: "string",
          description: "The name of the table",
        },
        data: {
          type: "object",
          description: "The record data to insert",
          additionalProperties: true,
        },
      },
      required: ["base_id", "table_name", "data"],
    },
  • src/index.ts:55-62 (registration)
    Registration of recordTools (containing 'insert_record') by spreading into the allTools array, which is used in ListToolsRequestSchema and CallToolRequestSchema handlers for listing and executing MCP tools.
    const allTools = [
      ...databaseTools,
      ...tableTools,
      ...recordTools,
      ...viewTools,
      ...queryTools,
      ...attachmentTools,
    ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('insert') but does not cover critical aspects such as required permissions, error handling, response format, or whether the operation is idempotent. This leaves significant gaps 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 with no wasted words, making it easy to parse. It is front-loaded with the core action, achieving optimal conciseness for its purpose.

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 mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error cases, and return values, failing to provide the completeness needed for effective tool invocation.

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, documenting all three parameters clearly. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline score for high schema coverage.

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 ('insert') and resource ('a single record into a table'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'bulk_insert' or 'update_record', which would require explicit comparison for a score of 5.

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 like 'bulk_insert' for multiple records or 'update_record' for modifications. It lacks context about prerequisites or typical use cases, offering minimal usage direction.

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

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/andrewlwn77/nocodb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server