Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Record order invoice correction

record_order_invoice_correction
Destructive

Attach a correction invoice or credit note to an existing order invoice after a refund, using a new invoice number and optional URL or provider.

Instructions

Attach a correction invoice (credit note: number, optional URL and provider) to an order that already has its invoice, e.g. after a refund. Allowed on canceled and refunded orders; the number must be new to the order.

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>",
      "number": "<number>"
    },
    "name": "record_order_invoice_correction"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
numberYesCorrection invoice number
orderIdYes
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is covered; the description adds value by disclosing the precondition set (canceled/refunded orders only) and the uniqueness constraint ('the number must be new to the order'). It does not describe failure behavior or whether a prior correction is replaced, which keeps it out of the top band.

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?

Two tight sentences with the core action front-loaded and the constraints following. The parenthetical '(credit note: number, optional URL and provider)' is slightly cramped but does real work by introducing the field set.

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?

For a destructive 4-parameter mutation with no output schema, the definition covers the essentials: what is attached, to which order, under what conditions, and the uniqueness rule. Missing details are secondary — return value and behavior when the order lacks an invoice — so it is nearly complete rather than fully so.

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 only 25%, with just 'number' documented, so the description has to compensate. It does partially by labeling url and provider as optional parts of the credit note and by adding a semantic rule for number ('must be new to the order'), but it leaves url format and provider meaning unexplained.

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?

The description names a specific verb and resource ('Attach a correction invoice (credit note)') and scopes it to 'an order that already has its invoice', which implicitly separates it from the sibling record_order_invoice. An agent can tell what is created and where it lands without opening the schema.

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 gives concrete usage context ('e.g. after a refund') and explicit eligibility rules ('Allowed on canceled and refunded orders'), which is stronger than most mutation tools. It stops short of naming an alternative tool or stating what to do when the order is not canceled/refunded, so it is clear context without full routing.

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

Deploy Server

Other Tools