Conecto

Change a draft order, or mark it sent

purchasing_update_order

Change a draft: its supplier, lines (they replace the old ones), currency, expected delivery date, stock location or notes. mark_sent: true records it as sent without emailing anyone (you sent it some other way): it takes the next number (PO-0001 on, without gaps) and its PDF is made. A sent order no longer changes; to email it, use purchasing_send_order instead. Costs $0.01 per call; nothing if it fails.

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": "<order>"
    },
    "name": "purchasing_update_order"
  }
}

Input Schema

Name	Required	Description
`lines`	No
`notes`	No
`order`	Yes	The order_id, or the order's number like "PO-0007".
`currency`	No	ISO 4217, e.g. "EUR". Default: the supplier's.
`location`	No
`supplier`	No	A supplier_id, or the supplier's name.
`mark_sent`	No
`expected_on`	No	YYYY-MM-DD, or null.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds significant behavior beyond the annotations: lines replace existing lines, mark_sent records the order as sent without emailing, assigns the next number without gaps, and generates the PDF. It also discloses that sent orders are immutable and that each call costs $0.01, with no charge on failure. These are exactly the operational details an agent needs before invoking a mutation tool.

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 three dense but well-structured sentences. It front-loads the primary update behavior, then explains mark_sent, then adds immutability, the sibling alternative, and cost. Every sentence earns its place with no filler.

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?

With no output schema and eight parameters, the description gives strong coverage of mutation semantics, cost, failure behavior, immutability, and the correct alternative tool. It stops short of describing the return value or explicitly confirming that unspecified fields remain unchanged, but those are minor omissions for a well-instrumented mutation tool.

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 description coverage is 50%, so the description must carry some weight. It names the updatable fields (supplier, lines, currency, expected delivery date, stock location, notes) and adds key semantics for lines ('they replace the old ones') and mark_sent (numbering/PDF/no email). It does not explicitly describe the required order parameter or clarify partial-update behavior for omitted fields, but it compensates well overall.

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 starts with a specific verb and resource ('Change a draft: its supplier, lines, currency...') and explicitly covers the special mark_sent action. It distinguishes the tool from purchasing_send_order by saying the latter is for emailing the order. An agent can identify exactly what this tool changes 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 Guidelines5/5

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

It states the core use case (changing a draft), the special mark_sent use case, and the key exclusion: 'A sent order no longer changes.' It also names the alternative explicitly: 'to email it, use purchasing_send_order instead.' That is explicit when-to-use and when-not-to-use guidance.

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

All Conecto 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?