fleetsync-mcp

fleetsync_update_order

Update an existing FleetSync order by order number, modifying client details, address, phone, email, date, or notes.

Instructions

Update an existing FleetSync order. Requires: Number. Optional fields to update: Client, Address, Phone, Email, Date, Note.

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": {
      "Number": "<Number>"
    },
    "name": "fleetsync_update_order"
  }
}

Input Schema

Name	Required	Description
`Date`	No	Delivery date in YYYY-MM-DD format
`Note`	No	Order notes
`Email`	No	Client email
`Phone`	No	Client phone number
`Client`	No	Client name
`Number`	Yes	Order number to update
`Address`	No	Delivery address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It communicates that the tool updates an existing order and requires a Number, but it does not disclose partial-update semantics, error handling for missing orders, or return value behavior.

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, front-loaded sentence that immediately states the action and resource. It leads with the core purpose and lists additional details without unnecessary wording.

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?

Given the simple update operation and full schema coverage, the description adequately explains what the tool does and what is needed to invoke it. It lacks return-value or error-behavior information, but those are not critical for a straightforward update tool.

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?

The input schema already describes all parameters with 100% coverage, so the description adds no new semantic detail. It restates the required Number and lists optional fields, but this adds no value beyond the schema.

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 uses the specific verb 'update' with the resource 'FleetSync order', clearly distinguishing it from sibling create/delete/get tools. It also enumerates the exact fields available for update, removing ambiguity about scope.

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 explicitly states the required parameter (Number) and lists optional updatable fields, giving clear operational guidance. It does not explicitly compare against sibling tools, but the phrase 'existing FleetSync order' implies it should not be used for creation or deletion.

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

Deploy Server