Microsoft Business Central MCP Server

delete_item

Remove a record from a specified Business Central resource by providing its ID and resource name.

Instructions

Delete an item from 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_id": "<item_id>"
    },
    "name": "delete_item"
  }
}

Input Schema

Name	Required	Description	Default
`item_id`	Yes	The ID of the item to delete
`resource`	Yes	The resource name (e.g., customers, contacts)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must convey behavioral traits. It merely restates the action 'Delete' without describing the deletion's effects, reversibility, or any required confirmation.

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, straightforward sentence with no unnecessary words. It's appropriately front-loaded and easy to parse.

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?

The tool has no output schema and no annotations, but it's a simple delete with only two parameters. The description covers the basic action but lacks context about the target resource type or the deletion's outcome, which is a gap. Still, the schema fills in the parameters, making it minimally viable.

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?

Both parameters are fully described in the schema. The description adds no additional meaning about item_id or resource, so it doesn't exceed the baseline for high schema coverage.

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?

Clearly states the action ('Delete') and system context ('Business Central'), which distinguishes it from sibling tools like create/update. However, 'item' is generic and doesn't indicate the resource parameter, so it's slightly less precise than ideal.

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 information about when to use this tool, such as requiring an existing item or not using for bulk operations. No exclusions or alternative tool references.

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

Deploy Server