John's Essentials

convert_sqlite

SQLite Converter — Export a SQLite database (.db/.sqlite) to CSV, JSON or Excel. A database holds many tables, so the output adapts: CSV gives one file per table (zipped when there are several), JSON gives rows as objects (keyed by table when there are several), and Excel gives ONE workbook with one worksheet per table. Pass an optional 'table' to export just one. [category: convert]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	Yes	What you want back. A database holds several tables, so the shape follows: CSV gives one file per table (zipped if there is more than one), Excel gives one workbook with a sheet per table, JSON gives the rows as records.	csv
`file`	Yes	SQLite database file.
`table`	No	Optional: export only this table (must match a table in the database).
`strict`	No	Stop rather than hand back a partial export. Off by default: a very large database comes back with whatever we could reach, and a note saying what was left out.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / table / x-ui
```
Added value: +{
+  "unset_label": "All tables"
+}
```

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / strict

Added value: +{
+  "default": false,
+  "description": "Stop rather than hand back a partial export. Off by default: a very large database comes back with whatever we could reach, and a note saying what was left out.",
+  "title": "Refuse partial answers",
+  "type": "boolean"
+}

addedInput schema / properties / to / default
```
Added value: +"csv"
```

changedInput schema / properties / to / description

Previous value: -"With 2+ tables, csv arrives as a ZIP of per-table CSVs — pass 'table' when a downstream step needs one plain CSV. xlsx = always one file."New value: +"What you want back. A database holds several tables, so the shape follows: CSV gives one file per table (zipped if there is more than one), Excel gives one workbook with a sheet per table, JSON gives the rows as records."

First observedSep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Although annotations only provide readOnlyHint=false and destructiveHint=false, the description adds significant behavioral context: it details how output adapts per format (CSV zipped when multiple tables, JSON keyed by table, Excel one workbook per sheet) and discloses the strict parameter's partial-export behavior, including what happens on very large databases. This goes beyond the sparse annotations and helps set expectations.

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 dense but every sentence earns its place: purpose first, then output adaptation rules, then the optional table parameter, and a category tag. It is front-loaded with the core intent and avoids redundant filler. Despite being slightly long, it packs useful information without confusion.

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?

With no output schema, the description carries the burden of explaining what the caller gets. It explains the output shapes for all three formats and the optional table-scoping and strict partial-export behavior. It does not specify the exact return container type (e.g., whether JSON is a single file or string), but given the parameter richness and schema coverage, the definition is sufficiently complete for an agent to call it correctly.

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 the baseline is 3. The description largely mirrors what the schema already says about 'to' (multi-table output shape), 'table' (optional single-table export), and 'strict' (refuse partial answers). It does not add new parameter meaning beyond an organizational overview, so 3 is appropriate.

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 opens with a precise verb and resource: 'Export a SQLite database (.db/.sqlite) to CSV, JSON or Excel.' This clearly states what the tool does and the resource it operates on. The specificity to SQLite inherently distinguishes it from generic siblings like convert_file and convert_data, so an agent can select it correctly without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use the tool: when a SQLite database needs conversion to CSV, JSON, or Excel. It also explains the multi-table behavior and the optional 'table' parameter for exporting a single table, which guides usage. It does not explicitly name alternatives or exclusions, but the input resource is specific enough to make usage obvious.

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

All John's Essentials tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?