Copilot Desktop MCP

Overview Schema Source Related Servers Discussions Admin

Create Sqlite

create_sqlite

Create a SQLite database file with defined tables, columns, and rows. Use it to generate .db or .sqlite files, with optional overwrite of existing files.

Instructions

Create a SQLite database file (.db or .sqlite). tables maps table names to {"columns": ["col1", "col2"], "rows": [[val1, val2], ...]}.

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": {
      "path": "<path>",
      "tables": "<tables>"
    },
    "name": "create_sqlite"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`tables`	Yes
`overwrite`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it is silent on the important behaviors: what happens when `path` already exists, that `overwrite` (default false) controls clobbering, whether parent directories are created, and whether this operation is destructive to existing data. It only conveys the file format, which is the least risky piece of information.

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?

Two short sentences, purpose front-loaded, with the nested data shape immediately after. Nothing is redundant and nothing pads the definition.

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?

An output schema exists, so return values need not be described, and the nested `tables` contract is explained. The remaining hole is the overwrite/failure semantics for an existing path, which matters for a file-creating mutation tool with no annotations.

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 0%, so the description must compensate, and it does the most valuable part by spelling out the nested `tables` shape ({"columns": [...], "rows": [[...]]}) that the bare schema leaves as an opaque additionalProperties object. However, `path` and `overwrite` receive no explanation, so the coverage gap is only partly closed.

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?

States a specific verb and resource ('Create a SQLite database file') and adds the accepted file extensions (.db or .sqlite), which is concrete and unambiguous. It does not differentiate itself from format-sibling creators like create_excel or create_archive, but the resource type is distinctive enough for an agent to select correctly.

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 when-to-use or when-not-to-use guidance at all; the agent must infer that this is the tool for producing a SQLite file rather than a PDF, DOCX, or archive. The existence of the `overwrite` flag is never tied to any guidance about overwriting versus failing, which is exactly the decision an agent needs help with.

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

Deploy Server