Skip to main content
Glama
Sign In
SQLite MCP Server

SQLite MCP Server

by stevefordev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_record

Insert a new record into a table, creating the table with default columns if it does not already exist.

Instructions

Add a new record to the specified table in the database. If the table doesn't exist, it will be created with columns: id, title, content, and created_at.

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": {
      "db_path": "<db_path>",
      "table_name": "<table_name>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "add_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
db_pathYes
table_nameYes
titleYes
contentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the automatic table creation with specific columns, but does not address behavior if the table exists with different schema or error conditions.

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 two sentences, front-loads the main purpose, and adds conditional behavior without any fluff. Every sentence earns its place.

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

Completeness3/5

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

Given 0% schema coverage and no annotations, the description explains the core function and auto-creation, but lacks information about return values (even though output schema exists) and error conditions.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain parameters. It mentions record fields (title, content) but does not explain db_path or table_name, leaving their meaning and constraints unclear.

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 tool adds a record to a specific table and handles automatic table creation with fixed columns. This distinguishes it from siblings like list_tables or describe_table.

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives like execute_query; it only implies its use for adding records, but does not exclude other methods.

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