Simpler.Asia

sales_settings_numbering_set

[REQUIRES APPROVAL] Sets where a document type's numbers continue, for example after moving from another invoicing tool. doc_type: invoice, quote, credit_note, debit_note or receipt. next_number is the sequence number the next document gets (42 prints as INV-2026-042). Numbering only moves forward: a number at or below the last one used or skipped is refused with VALIDATION_ERROR naming that number, and nothing changes. prefix sets the credit_note, debit_note or receipt prefix; invoice and quote prefixes are invoice_prefix and quote_prefix on sales_settings_upsert. An agent call waits for the owner's approval. Read the current numbers with sales_settings_numbering_read.

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": {
      "doc_type": "<doc_type>"
    },
    "name": "sales_settings_numbering_set"
  }
}

Input Schema

Name	Required	Description
`prefix`	No	credit_note, debit_note or receipt only: 1-10 letters or digits (plus . _ / -), printed before the year.
`doc_type`	Yes	Which document type's numbering to change.
`next_number`	No	The sequence number the next document of this type gets. Must be above the last number used or skipped.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond annotations: discloses the approval gate ('An agent call waits for the owner's approval'), the forward-only constraint, the exact failure mode (VALIDATION_ERROR naming the offending number) and its atomicity ('nothing changes'). These details are consistent with idempotentHint=false and destructiveHint=false.

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?

Densely packed but front-loaded with the [REQUIRES APPROVAL] flag and the core action. Every sentence carries information, though the middle sentences run long and could be split for scanability.

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 3-parameter mutation with an approval gate and no output schema, the description covers the constraint, failure behavior, and sibling routing. Only the success result (what is returned after the change is applied) is left unstated.

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 100%, so baseline is 3, but the description adds a concrete formatting example ('42 prints as INV-2026-042') and reiterates which doc types accept a prefix. It adds meaning without fully documenting optionality or defaults.

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 ('Sets where a document type's numbers continue') plus the motivating scenario (migrating from another invoicing tool). It is clearly distinguished from sales_settings_numbering_read (read) and sales_settings_upsert (which owns invoice/quote prefixes).

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

Usage Guidelines5/5

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

Explicitly routes the agent: read current numbers with sales_settings_numbering_read, and set invoice/quote prefixes via sales_settings_upsert instead of this tool. It also names the condition under which the tool is needed (moving from another invoicing tool).

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?