Skip to main content
Glama
andrewlwn77
by andrewlwn77

get_base_info

Retrieve detailed information about a specific NocoDB base or project by providing its ID to access configuration, structure, and metadata.

Instructions

Get detailed information about a specific base/project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
base_idYesThe ID of the base/project

Implementation Reference

  • The handler function that fetches detailed information about a specific NocoDB base using the provided base_id and returns structured base details.
    handler: async (client: NocoDBClient, args: { base_id: string }) => {
      const base = await client.getBase(args.base_id);
      return {
        base: {
          id: base.id,
          title: base.title,
          status: base.status,
          created_at: base.created_at,
          updated_at: base.updated_at,
        },
      };
    },
  • Input schema defining the required base_id parameter as a string.
    inputSchema: {
      type: "object",
      properties: {
        base_id: {
          type: "string",
          description: "The ID of the base/project",
        },
      },
      required: ["base_id"],
    },
  • Tool definition registered in the databaseTools array.
    {
      name: "get_base_info",
      description: "Get detailed information about a specific base/project",
      inputSchema: {
        type: "object",
        properties: {
          base_id: {
            type: "string",
            description: "The ID of the base/project",
          },
        },
        required: ["base_id"],
      },
      handler: async (client: NocoDBClient, args: { base_id: string }) => {
        const base = await client.getBase(args.base_id);
        return {
          base: {
            id: base.id,
            title: base.title,
            status: base.status,
            created_at: base.created_at,
            updated_at: base.updated_at,
          },
        };
      },
    },
  • src/index.ts:55-62 (registration)
    Combines all tool sets including databaseTools into allTools, which is used for MCP tool listing 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get detailed information' implies a read-only operation, it doesn't specify what 'detailed information' includes, whether authentication is required, rate limits, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information (action and target).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with one parameter and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what information is returned, error handling, or usage constraints to be fully complete.

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 the single parameter 'base_id' fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema already provides (e.g., format examples, validation rules, or what constitutes a valid base/project ID).

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 action ('Get detailed information') and the target resource ('about a specific base/project'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from similar siblings like 'get_table_info' or 'get_record', which also retrieve information about specific resources.

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. With siblings like 'list_bases' (for listing bases) and 'get_table_info' (for table details), there's no indication of when this base-level information tool is appropriate versus other information-retrieval tools.

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