Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Record order invoice

record_order_invoice
Destructive

Attach an invoice number, optional URL, and provider to an existing order for billing records and traceability.

Instructions

Attach an invoice (number, optional URL and provider) to an 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
numberYesInvoice number
orderIdYes
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "orderId",
      +  "number"
      +]
  2. First observedv0.73.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is covered, but the destructive flag is unexplained: the description never says whether attaching an invoice overwrites an existing one, or whether the action is reversible. For a tool flagged destructive, that missing disclosure is a real gap.

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?

A single front-loaded sentence with no filler; the parenthetical efficiently lists the invoice fields. It is appropriately sized, though brevity is partly the cause of the disclosure gaps rather than a virtue.

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?

For a four-parameter mutation tool with a destructive annotation and no output schema, the definition says nothing about effects on existing invoice data, error cases such as duplicate invoices, or permissions. It falls well short of what an agent needs to invoke it confidently.

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 only 25% (only number is documented as 'Invoice number'), so the description must compensate somewhat. It does clarify that url and provider are optional, but orderId is left entirely unexplained despite being required.

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 states a concrete verb and resource set: attach an invoice to an order, with the three invoice fields named. That is clear enough to select it over generic record tools, but it does not distinguish itself from the sibling record_order_invoice_correction.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. A sibling named record_order_invoice_correction strongly suggests a correction path for amending invoices, yet the description never tells the agent which one to pick.

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