SQL Server MCP Server

insert_record

Insert a record into a SQL Server table by specifying the table name, optional schema, and a dictionary of column names and values. Simplifies data creation with direct, table-specific input.

Instructions

Insert a single record into a database table (Create).

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_name": "<table_name>",
      "data": "<data>"
    },
    "name": "insert_record"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Dictionary mapping column names to values (e.g., {"first_name": "John", "age": 30}).
`table_name`	Yes	Target table name.
`schema_name`	No	Target schema name (default: 'dbo').	dbo

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 19, 2026

TDQS

B3/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It lacks any mention of side effects, validation, error handling, or data integrity checks, leaving the tool's behavior entirely opaque.

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 a single, succinct sentence that directly conveys the core function without unnecessary verbosity or structural complexity.

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

Completeness2/5

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

The description is too minimal to be complete. It does not clarify the tool's role within the broader set of database operations, nor does it address potential edge cases or expected behavior, despite the availability of sibling tools that could benefit from explicit differentiation.

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?

The input schema already describes all parameters (coverage 100%), so the baseline is 3. The description adds no additional meaning about parameter relationships, constraints, or usage nuances beyond the schema.

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 action ('Insert a single record') and the resource ('database table'), with the '(Create)' clarifying the CRUD operation. It effectively distinguishes from 'bulk_insert_records' by specifying 'single record'.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives like 'bulk_insert_records' or 'execute_sql'. It only describes the action without contrasting use cases or prerequisites.

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

Deploy Server