OpenCart MCP Server

Overview Schema Source Related Servers Discussions Admin

Update Order Status

update_order_status

Change an OpenCart order's status and append a history entry, optionally marking the customer as notified without sending email.

Instructions

Change an order's status and append an order-history entry — the same thing the admin status dropdown does. notify=True marks the history row as customer-notified but does NOT send the email itself. Use get_order_statuses to look up status IDs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`notify`	No
`comment`	No
`order_id`	Yes
`order_status_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two non-obvious behaviors: a history row is always appended, and notify=True only flags the row rather than sending email. However, it omits permissions/auth requirements, error conditions, and whether the change is reversible.

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?

Three short sentences, front-loaded with the primary action and side effect, then the notify caveat, then the lookup hint. Slightly dense with em-dash clauses but nothing wasted.

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

Completeness4/5

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

An output schema exists so return values need no explanation, and the description covers the key mutation side effects for a tool with zero annotation support. It is close to complete, missing only auth/precondition detail for a write operation.

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 0%, so the description must compensate. It explains the counterintuitive notify semantics and implies order_status_id must come from get_order_statuses, but the comment parameter and its default are never mentioned, leaving half the parameters undocumented.

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?

States a specific verb and resource ('Change an order's status') and names the exact side effect ('append an order-history entry'), with the admin dropdown analogy making the scope unambiguous. It is clearly separable from siblings like update_product or update_setting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to get_order_statuses for status IDs, which is the real prerequisite for this call. It stops short of stating when not to use this tool or what to do if the order is already in that status.

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