mcp-server-smallinvoice

send_order_confirmation_by_post

Physically send an order confirmation by post with customizable color, duplex or simplex printing, and priority or economy speed. Irreversible action.

Instructions

Sends specified order confirmation by post (SENDS BY POST — irreversible)

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": {
      "order_confirmation_id": "<order_confirmation_id>",
      "palette": "<palette>",
      "print": "<print>",
      "speed": "<speed>"
    },
    "name": "send_order_confirmation_by_post"
  }
}

Input Schema

Name	Required	Description
`order_confirmation_id`	Yes	order confirmation ID
`palette`	Yes	palette; possible values: C - colour, BW - black&white
`print`	Yes	printing type; possible values: D - duplex (two-sided), S - simplex (one-sided)
`speed`	Yes	sending speed; possible values: P - priority, E - economy

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds the key behavioral trait 'irreversible', which is not captured by annotations (destructiveHint: false). It also clarifies the physical sending method. No contradictions with annotations.

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?

Single sentence, no redundancy. Every word adds value: action, resource, method, and key behavioral note (irreversible).

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?

The description is minimal but covers the essential purpose and irreversibility. No output schema exists, but the action is straightforward. Some might desire details on success/failure or post-sending state, but the tool is adequately specified for selection.

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 100%, so baseline 3 applies. The description does not add further parameter details, but the schema already documents each parameter adequately.

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 clearly states the action ('sends') and the resource ('order confirmation') and specifies the method ('by post'). It distinguishes from the email sibling tool, and adds the important qualifier 'irreversible'.

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?

The description implies when to use (send by post) and flags irreversibility, guiding cautious use. It does not explicitly state when not to use or name alternatives, but the sibling list makes the alternative (send_order_confirmation_by_email) obvious.

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

Deploy Server