Baasix MCP Server

baasix_create_item

Add a new item to a specified collection by supplying collection name and item data. Use this tool to insert records into Baasix backend collections.

Instructions

Create a new item in a collection

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": {
      "collection": "<collection>",
      "data": "<data>"
    },
    "name": "baasix_create_item"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Item data
`collection`	Yes	Collection name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'Create' only implies mutation; it does not state whether creation validates against a schema, auto-generates IDs, overwrites existing data, requires authentication, or what side effects occur.

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 a single short sentence with no filler and front-loads the verb and object. It is concise, though the brevity comes at the cost of useful behavioral detail.

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?

Without annotations or an output schema, the description does not tell the agent what happens after calling the tool, such as the returned item/ID, error behavior, or prerequisites like an existing collection/schema. For a mutating operation, this is incomplete.

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%, since both 'data' and 'collection' have descriptions in the schema. The description adds only generic context that the item belongs to a collection, so it provides little meaning beyond what the schema already offers.

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 uses a specific verb ('Create') and a clear resource ('a new item in a collection'), which distinguishes it from sibling item operations like update_item, delete_item, and list_items. It is not a pure tautology because it clarifies the item belongs to a collection, though it is still very close to the tool name.

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 guidance about when to use this tool versus alternatives. It does not mention that a schema/collection must already exist, that this is the write counterpart to get/list/update/delete, or any conditions that would make this tool the right choice.

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

Deploy Server