IRIS MCP Blueprint

insert_data

Add a new record to a database table by specifying the table name, optional schema, and column values.

Instructions

Insert a single row into a table. Args: ctx: The context of the tool call. table_name: The name of the table to insert the data into. values: The values to insert into the table. table_schema: The schema of the table to insert the data into.

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>",
      "values": "<values>"
    },
    "name": "insert_data"
  }
}

Input Schema

Name	Required	Default
`table_name`	Yes
`values`	Yes
`table_schema`	No	SQLUser

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jun 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits like error handling, side effects, or concurrency behavior. It only states the basic action without any depth about what happens during insertion (e.g., duplicate key handling).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively short and front-loaded with the main action. The 'Args' section adds structure, though it could be slightly more concise by removing the redundant 'Args:' line. Overall, it efficiently conveys the core purpose without excessive text.

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 the existence of an output schema (though not detailed), the description lacks information about return values or expected behavior. The tool has 3 parameters (2 required) and is straightforward, but additional context about data validation, success/failure indicators, or typical use cases would improve completeness. It is minimally adequate.

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?

While the description lists parameters in an 'Args' block and provides brief comments (e.g., 'The values to insert into the table'), it lacks important semantic details. For instance, the 'values' parameter format (likely a dictionary) is not specified, and 'table_schema' defaults to 'SQLUser' with no explanation. With 0% schema description coverage, the description should compensate but fails to provide sufficient meaning beyond the schema.

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?

The description clearly states 'Insert a single row into a table' which specifies the verb and resource. However, it does not differentiate from sibling tools like 'fetch_data' or 'save_global', which could cause confusion. The purpose is clear but lacks sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use 'import_csv_to_iris' for bulk inserts or how to handle schema validation. There are no prerequisites or contextual hints.

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