mcp-server-smallinvoice

change_order_confirmation_status

Update an order confirmation's status to draft, sent, billed, or deleted to manage its lifecycle in smallinvoice.

Instructions

Changes status of specified order confirmation

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>",
      "status": "<status>"
    },
    "name": "change_order_confirmation_status"
  }
}

Input Schema

Name	Required	Description
`order_confirmation_id`	Yes	order confirmation ID
`status`	Yes	status of order confirmation, possible values: DR - draft, S - sent, B - billed, D - deleted (but still visible)
`date_time`	No	optional date time of a change in Y-m-d H:i:s format (if none specified current date time will be taken)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description states 'Changes status', aligning with the annotation's readOnlyHint=false, but adds no further behavioral context beyond what annotations provide. The date_time parameter's optional nature and the exact implication of changing status (e.g., side effects, reversibility) are not disclosed, so the description adds moderate value.

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?

The description is a single, straightforward sentence that efficiently conveys the tool's core action. No unnecessary words or repetition, making it easily scannable.

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?

Given the lack of an output schema and the presence of siblings, the description is too minimal. It fails to explain the behavior of the date_time parameter, how the status change affects related data, or what the return value indicates. The description leaves significant gaps for an agent to infer.

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 100%, with all three parameters described in the input schema. The description does not add additional meaning beyond the schema's parameter descriptions, leading to a baseline score of 3.

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 'Changes status of specified order confirmation' clearly states a specific verb ('Changes') and resource ('status of order confirmation'). It effectively distinguishes from sibling tools like change_invoice_status, change_offer_status, etc., by targeting order confirmations specifically.

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?

No guidance is provided on when to use this tool versus alternatives such as update_order_confirmation or other change_status tools. There is no mention of prerequisites, context, or when not to use it, leaving the agent without direction.

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

Deploy Server