Skip to main content
Glama
lancedb

LanceDB MCP Server

Official
by lancedb

table_details

Retrieve metadata details of a LanceDB table, including schema and row count, by specifying the table name and database URI.

Instructions

Get the details of a LanceDB table.

Args:

    table_name (str): The name of the table to get the details of. Defaults to "lancedb_table".
    db_uri (str): The URI of the LanceDB database. Defaults to "~/lancedb".

Returns:
    dict: A dictionary of the table details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameNo
db_uriNo
Behavior2/5

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

With no annotations, the description should disclose side effects, permissions, or return behavior, but it only states that it returns a dict without further details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description uses a docstring format with Args/Returns sections, which is longer than necessary and includes default values that could be inferred.

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?

The description lacks explanation of what 'details' are returned, no output schema exists, and no edge cases or error conditions are mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since schema description coverage is 0%, the description compensates by clarifying the default values for both parameters and the purpose of table_name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 the resource 'details of a LanceDB table', which is specific and distinguishes it from sibling tools like 'ingest_docs' and 'query_table'.

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, nor any exclusions or prerequisites.

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/lancedb/lancedb-mcp-server'

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