Skip to main content
Glama
MCP SQLite Server

MCP SQLite Server

by obiokoye

Describe table

describe_table
Read-only

Shows a SQLite table's columns—names, types, primary-key and NOT NULL status—and foreign keys so you can inspect schema structure before writing queries.

Instructions

Show a table's columns (name, type, primary key, not null) and foreign keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>"
    },
    "name": "describe_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name from list_tables

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description need not restate that it is a read. It does add value by disclosing the concrete return contents (name, type, primary key, not null, foreign keys), effectively documenting the output shape since no output schema exists. It says nothing, however, about behavior for unknown tables or non-table objects like views.

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?

One short sentence, front-loaded with the action and immediately followed by the specific returned attributes. Nothing is redundant or padded.

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

Completeness4/5

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

For a single-parameter metadata read with annotations covering safety, the definition supplies enough: what it returns, and the field set an agent would need to interpret results without an output schema. Only edge-case behavior (missing table, views) is left unstated.

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?

Only one parameter with 100% schema description coverage, which already explains that the value comes from list_tables, so the schema carries the burden. The description adds no format or validation detail beyond the schema; baseline 3 applies.

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?

A specific verb ('Show') plus a clearly scoped resource ('a table's columns ... and foreign keys'), and the parenthetical enumerates exactly which attributes are returned. It is easy to distinguish from list_tables and read_query on the basis of the described operation, though the description never names those siblings explicitly.

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?

There is no statement of when to use this versus list_tables or read_query, and no prerequisites or exclusions are given. The only routing hint lives in the schema ('Table name from list_tables'), not in the description itself, so guidance is merely implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools