Skip to main content
Glama
andrewlwn77
by andrewlwn77

get_record

Retrieve a specific database record by providing its ID, base ID, and table name to access stored data in NocoDB.

Instructions

Get a single record by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project
table_nameYesThe name of the table
record_idYesThe ID of the record

Implementation Reference

  • Handler function for the 'get_record' tool. It takes base_id, table_name, and record_id, calls the NocoDB client's getRecord method, and returns the record.
    handler: async (
      client: NocoDBClient,
      args: {
        base_id: string;
        table_name: string;
        record_id: string;
      },
    ) => {
      const record = await client.getRecord(
        args.base_id,
        args.table_name,
        args.record_id,
      );
      return {
        record,
      };
    },
  • Input schema defining the parameters for the 'get_record' tool: base_id, table_name, and record_id.
    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",
        },
        record_id: {
          type: "string",
          description: "The ID of the record",
        },
      },
      required: ["base_id", "table_name", "record_id"],
    },
  • src/index.ts:55-62 (registration)
    Registration of tools including recordTools (which contains 'get_record') into the allTools array used by the MCP server for tool discovery and execution.
    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 full burden for behavioral disclosure. It only states the basic action ('Get a single record') without mentioning permissions, error handling, rate limits, or response format. For a read operation with zero annotation coverage, this leaves significant behavioral gaps unexplained.

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 perfectly concise at six words, front-loading the essential information ('Get a single record by ID') with zero wasted words. Every element earns its place, making it immediately scannable and understandable.

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 tool's moderate complexity (3 required parameters) and lack of both annotations and output schema, the description is insufficiently complete. It doesn't explain what a 'record' contains, how IDs are formatted, what happens if the record doesn't exist, or what the return value looks like. For a core retrieval tool in this context, more contextual information is needed.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond implying 'record_id' is the primary identifier. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to.

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 ('Get') and resource ('a single record by ID'), making the purpose immediately understandable. It distinguishes this from bulk retrieval tools like 'list_records' or 'search_records' by specifying 'single record'. However, it doesn't explicitly differentiate from similar single-record tools like 'get_attachment_info' or 'get_table_info', which prevents a perfect score.

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 when to choose 'get_record' over 'list_records' for multiple records, 'search_records' for filtered queries, or 'query' for complex retrievals. There are no prerequisites or contextual cues about appropriate use cases.

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