toolsdatabase inspect

Database Inspect

database_inspect

Inspects a local SQLite database without changing it. Returns table names, column definitions, indexes, foreign keys, database size, and optional row counts. It opens the database read-only and never executes user-supplied SQL. Use when: an agent needs to understand a local SQLite schema before proposing a query, migration, or data-analysis step. Scope: local SQLite files only. Read-only. Not for: running SQL queries or modifying data; use a separate guarded query tool when that is available. PostgreSQL, MySQL, and remote database URLs are not supported by this tool.

How to use database_inspect

Provide only the required inputs below. Start with the smallest scope that answers the task, then review the risk properties before an agent executes the call.

Risk and execution properties

Read only: yes

Destructive: no

Idempotent: yes

Open world: no — operates locally or through configured services

Inputs

pathstringrequired

Absolute or relative path to a local SQLite database file. Example: '/Users/me/project/data/app.db'.

include_row_countsboolean

If true, count rows in each table. This can be slow for large databases. Default: false.

Default: false

tablestring

Optional exact table name to inspect. Omit to inspect all tables, up to 100.

Example input

{
  "path": "<string>",
  "include_row_counts": false,
  "table": "<string>"
}

Browse or search the full 74-tool reference to choose the smallest suitable capability.

Browse all tools →