D-Tools MCP Server

create_service_order

Create a new service order in D-Tools SI by specifying a required name and optional project, client, description, status, due date, and line items.

Instructions

Create a new service order in D-Tools SI. Requires a name; optionally accepts project, client, description, status, due date, and line items.

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": {
      "serviceOrder": "<serviceOrder>"
    },
    "name": "create_service_order"
  }
}

Input Schema

Name	Required	Description	Default
`serviceOrder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It states it creates a service order but does not disclose behavioral traits like whether it returns the created object, validation rules, authorization needs, or side effects. The minimal description leaves the agent guessing about the tool's 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 concise: two sentences with no wasted words. It front-loads the purpose and immediately states requirements and options. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested object, many optional fields, no output schema), the description is adequate but minimal. It tells what the tool does and what fields are available, but lacks details on default values, error handling, or output. For a create operation, it covers the essentials but not more.

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 0%, so description must compensate. It lists optional fields (project, client, description, status, due date, line items) adding meaning beyond the schema's property names. However, it does not explain the structure of line items or format of dates, leaving gaps that the schema itself (with nesting) doesn't fully clarify.

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 'Create a new service order' with a specific verb and resource, and distinguishes it from sibling tools like create_client or create_project. It also mentions the system (D-Tools SI) and lists key fields.

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

Usage Guidelines3/5

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

The description gives basic information (requires name, optional fields) but does not explicitly state when to use this tool versus alternatives, such as when to create a new order versus updating an existing one. It implies usage but lacks explicit guidance on prerequisites or exclusions.

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