Skip to main content
Glama
mcp-erp-server

mcp-erp-server

by aldemarluz

Update sales order status

sales_update_order_status
Idempotent

Move a sales order to a new status with a dry-run preview by default; set confirm=true to apply only valid transitions.

Instructions

Move a sales order to a new status. Without confirm=true this only returns a preview (dry run). Only valid transitions are accepted.

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": {
      "orderId": "<orderId>",
      "status": "<status>"
    },
    "name": "sales_update_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
confirmNoMust be true to actually write
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description adds genuinely new behavior: writes are opt-in via confirm=true and default to a non-mutating preview. It also discloses that invalid transitions are rejected rather than silently applied. It stops short of saying what the preview contains or what an invalid-transition response looks like.

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?

Three short sentences with the core action first, then the dry-run default, then the validation constraint. No filler, and the most important caveat (preview by default) is placed early.

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?

For a small 3-parameter mutation this covers the essentials, but with no output schema an agent still lacks what the dry-run preview returns and where the permitted transition graph comes from. The cancelled enum value also goes unaddressed in terms of impact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, with orderId undocumented and confirm carrying the only field description. The description compensates by explaining exactly what confirm=true changes (preview vs. actual write) and by adding the constraint that status must be a legal transition, which is meaning the enum alone does not convey.

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 opens with a specific verb and resource, 'Move a sales order to a new status', which is immediately distinguishable from the read-only siblings (sales_list_orders, sales_get_price). It does not explicitly name a sibling it displaces, but the mutating scope is unambiguous.

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?

It clearly states the primary usage decision: without confirm=true you get a preview/dry run, with it you perform the write. That is actionable context absent from the schema. It stops short of naming alternatives or saying how to obtain the set of valid transitions, so no exclusions are offered.

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