Microsoft Business Central MCP Server

create_item

Creates a new item in Microsoft Business Central by specifying the resource type (e.g., customers, contacts) and the item data to add.

Instructions

Create a new item in Business Central

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": {
      "resource": "<resource>",
      "item_data": "<item_data>"
    },
    "name": "create_item"
  }
}

Input Schema

Name	Required	Description	Default
`resource`	Yes	The resource name (e.g., customers, contacts)
`item_data`	Yes	The item data to create

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 7, 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 disclosing behavior. It only states 'Create a new item' without mentioning any side effects, permissions needed, error conditions, or how existing data might be affected. This is minimal transparency for a mutation tool.

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, concise sentence that gets to the point quickly. It is not verbose, but it lacks some detail that could be included without sacrificing brevity. Overall, it is appropriately sized for a simple create tool.

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?

Given the tool has two parameters including a nested object and no output schema, the one-sentence description is insufficient. It does not explain what 'item' means, how to structure item_data, or what the response will be. Sibling tool context suggests it is a generic create, but that is not conveyed.

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 coverage is 100% with both parameters described ('resource' and 'item_data'), so the schema already provides the essential meanings. The description adds no extra parameter context, but with full schema coverage, a baseline of 3 is appropriate.

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 the action (creating) and the resource ('new item in Business Central'), distinguishing it from sibling tools like update_item and delete_item. However, it does not clarify that the 'resource' parameter makes it a generic create tool for various entity types, which could cause slight ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as update_item or list_items. There is no mention of prerequisites, exclusions, or specific scenarios where this tool is appropriate, leaving usage inferred solely from the verb 'create'.

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

Deploy Server